A resync operation is required when the Production Volumes and Recovery Replica Volumes diverge. This occurs after a failure of the production server and a failover to the recovery server. When the application is started on the recovery server the updates result in a divergence from the data on the production server.
After restoring the original production server, use the resync operation to ensure that the production server data is current with the recovery server data.
To resynchronize the revived production server from the recovery server, on all servers (production, recovery):
rtdr -qC <Primary Context ID> resync
This command takes the following actions:
-
On the recovery server:
start aba for failover context
-
On the production server:
start aba for failover context start lca for failover context if there is a configured recovery server
-
On recovery server:
start lca for failover context
Note: The resync operation assumes the original production data was not lost, and is
available in its entirety after the production server is revived. If the production data
is lost, the statemap on the recovery server must be marked as dirty prior to
resync. This forces a complete region recovery and initializes the production
data.