Resynchronizing a failed Primary with the new Primary

Use the vxrds fbsync to resynchronize the failed Primary with the new Primary after it becomes available again after the takeover operation. This command uses failback logging on the new Primary to synchronize data volumes on the failed Primary with the data volumes on the new Primary.

Note:

This command can be run only if failback logging was enabled during takeover.

In the failback logging mode, Volume Replicator uses Data Change Maps (DCM) to track the changes happening on the new Primary while the original Primary is not available.

When the original Primary recovers, it needs to be synchronized with the new Primary by playing back the DCM on the new Primary. To receive the missing updates, the original Primary must first be converted to a Secondary. The vxrds fbsync command synchronizes the original Primary with the new changes on the new Primary by replaying the DCMs.

Note:

The data on the Secondary data volumes is inconsistent for the duration of the replay.

Use the vxrds fbsync command with the -wait option to make sure that the command waits until the resynchronization completes.

Note:

Do not use the vxrds fbsync command if the -autofb option was used at the time of the takeover.

Syntax for vxrds fbsync command

vxrds [-g <diskgroup>] [-wait] fbsync <rvg>

Example

vxrds -g vvrdg -wait fbsync rvg

More Information

Taking over the Primary role using the vxrds takeover command