Redundancy for a Juniper Networks Database
Protect SRC data by setting up a redundancy scheme for your Juniper Networks databases. Client applications control which database they connect to as their primary database and as their backup database.
Use the following guidelines to plan which databases are assigned primary or secondary roles, and which databases are primary or secondary neighbors:
- Each Juniper Networks database that is assigned a primary role should have at least one primary neighbor. Should a database assigned a primary role become inoperable, a client application fails over to a primary neighbor.
- Each database that is assigned a secondary role should have at least two primary neighbors.
- Applications that frequently perform write operations to the database should connect to databases that have a primary role. Applications that perform frequent write operations are the C-Web interface, the SRC CLI, back-office applications that provision data, and in some cases the SRC-ACP.
- Applications that rarely perform updates, such as the NIC and SAE, can communicate with databases assigned a secondary role. For example, you could configure the NIC and SAE to communicate with the local directory on a C-series platform, and configure the database on this system to have a secondary role.