> - Downloads
> - Recovering Data in a Community with One Primary Database and One Secondary Database (SRC CLI)
> - Related Topics
> - Recovering Data in a Community with One Primary Database and One Secondary Database with the C-Web Interface
> - Promoting a Secondary Database to a Primary Role in a Configuration with One Primary Database (SRC CLI)
> - Troubleshooting Data Synchronization for Juniper Networks Databases (SRC CLI)
> - Overview of the Juniper Networks Database

> # Recovering Data in a Community with One Primary Database and One Secondary Database (SRC CLI)

> In an environment in which a community includes one database assigned a primary role and another database assigned a secondary role, and the primary database is not operative, you must promote the secondary database to primary and reconfigure the inoperative primary database.

> 1. On the database that has a secondary role, set the role to primary.

>    For example, if the database on C2 has a secondary role:

>    `
>    user@C2# edit system ldap server community
>    [edit system ldap server community]
>    user@C2# set role primary
>    user@C2# commit
>    `

>    C2 already has C1 configured as primary neighbor.

> 2. On the existing database that has a primary role, remove the neighbor as secondary and add it as primary.

>    For example, to configure C1 as a primary database with C2 as a primary neighbor:

>    `
>    user@C1# edit system ldap server community
>    [edit system ldap server community]
>    user@C1# set role primary
>    user@C1# delete secondary-neighbors C2
>    user@C1# set primary-neighbors C2
>    user@C1# commit
>    `

> #### Published: 2009-09-25

> Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.