![]() |
![]() |
![]() |
![]() |
![]() |
This method is useful for low bandwidth networks or very large data sets. You can use the block-level backup and checkpoint method to synchronize the Secondary when a backup of the data is available and a checkpoint has been started on the Primary. You do not have to use the network to transfer the data. This method does have a risk of SRL overflow.
Make sure that the SRL is large enough to contain all the writes made by the application while synchronization is in progress. For instructions on how to resize the SRL, see Resizing the SRL.
Caution
During the process the checkpoint will overflow if the SRL fills up. To determine if the checkpoint has overflowed, issue the
vxrvg
cplist
rvg_name command on the Primary to display the list of valid checkpoints.
For detailed instructions, see Example—Synchronizing the Secondary using block-level backup.
To synchronize the Secondary using backup and Primary checkpoint
vxrvg
checkend
command:
After the RLINKs are attached, the Secondary remains inconsistent until it has received all of the accumulated updates up to the checkend. While the Secondary is inconsistent, the inconsistent
flag is set on the Secondary RLINK. After all updates up to the checkend have been received and applied at the Secondary, the inconsistent
flag is cleared.
Example—Synchronizing the Secondary using block-level backup
This example explains how to synchronize the Secondary RVG hr_rvg
on the Secondary host london
with the Primary RVG on host seattle
using block-level backup and checkpoint.
seattle
: