Break and reset database replication when you want to disable replication on your servers and return the Primary and Standby servers to stand-alone operation. First, use the Address Manager GUI on the Primary server to break replication. This will return the Primary server to stand-alone operation, and turn the Standby servers into Removed Standby servers that must be reset. After breaking replication in the Primary server GUI, use the Administration Console (CLI) on Standby servers to reset replication and return them to standalone operation. After completing these steps, all servers will be in stand-alone mode and database replication can be reconfigured.
Note: You must be an Address Manager administrator to break database
replication.
Note: If the Primary Address Manager server is offline, refer
to Forcibly resetting database replication.
-
Break database replication and return the Primary server to stand-alone
operation:
-
Reset replication on the Standby server(s):
- Connect to the Address Manager Administration Console (CLI) on the Standby server. For instructions on how to connect to the Administration Console, refer to Using the Administration Console.
- Log in as the administrator.
-
From Main Session mode, type
configure database
and pressENTER
. -
Type
reset replication
and pressENTER
. -
Type yes and press ENTER
to confirm the replication reset. The following message appears when the
server is set to standalone mode:
Reset replication successful: now a standalone server
. - Repeat the Administration Console reset steps above for additional Standby servers. Each Standby server must be reset individually.
After performing the steps above, all servers have been returned to standalone
operation and contain the information that was replicated until the break was performed.
Note: After resetting replication on the Standby servers via the Administration
Console, scheduled deployment on the Standby servers is disabled.
Note: After
breaking replication, BlueCat recommends performing a full deployment to all managed
DNS/DHCP Servers.