When the Data Mover cluster is running in active mode, the sync monitor keeps the repositories in synchronization. Synchronization keeps components on the secondary server with an up-to-date repository ready to take over if a failover occurs.
If Data Mover is configured to log alerts to server management, alerts are triggered when the repositories are no longer in synchronization. Checking dmSync.log and Postgres logs help identify the root cause to determine the appropriate corrective action.
Re-synchronize the repositories by performing the following:
- On the primary daemon server, run the dmcluster switchback command and follow the prompts:
Prompt Action Do you need to sync up the two repositories? [y or n] Enter y to sync up. Enter 1 to back up the primary repository (DM1) to the secondary repository (DM2).
Enter 2 to back up the secondary repository (DM2) to the primary repository (DM1).
[1 or 2]
Provide the direction of sync up by entering either 1 or 2. - From the primary daemon server, run the dmcluster status command to verify all services are running in active mode as expected.It may take a few minutes for all services to transition. Run dmcluster status as needed until the results are as expected. Monitor progress in dmFailover.log on the currently active daemon and monitor servers.