After a takeover, if the rlink is disconnected during the resync of the original Primary, the data on the original Primary may be out of sync.

Article:TECH22239  |  Created: 2002-01-27  |  Updated: 2002-01-23  |  Article URL http://www.symantec.com/docs/TECH22239
Article Type
Technical Solution


Environment

Issue



After a takeover, if the rlink is disconnected during the resync of the original Primary, the data on the original Primary may be out of sync.

Solution



When the original Primary comes back up after the original Secondary takes over as the new Primary, and a resync is being performed to resynchronize the original Primary from the new Primary, and the RLINK disconnects, the data on the original Primary may be out of sync.

For example, this problem can occur if the following is performed:

On the Primary:
1.  Pause the rlink
# vxrlink pause rlink1
2.  Partially fill the Storage Replicator Log (SRL)
# dd if=/some/data of=/dev/vx/rdsk/diskgroup1/datavolume1
3.  Start draining the SRL
# vxrlink resume rlink1
4.  Reboot the system
# reboot

On the Secondary:
5.  Wait for rlink flag status "disconnected"
# vxprint -Pl rlink2
6.  Take over as the new Primary
# vxrvg -F makeprimary rvg1
7.  Wait for original Primary to reboot
8.  Resync the original Primary
# vxrvg resync rvg1
9.  Wait for rlink flag status "resync_started"
# vxprint -Pl rlink2
10. Reboot the new Primary
# reboot

If the data on the original Primary is out of sync, a full resynchronization of the original Primary is required to restart the replication.  Refer to VERITAS Volume Replicator (VVR) Administrator's Guide for details on the full resynchronization procedure.

To verify if the data on Primary and the Secondary is the same, refer to the procedure described in TechNote 231804, link provided below under "Related Documents".

This problem can occur on VERITAS Storage Replicator for Volume Manager (SRVM) 3.0.2, VVR 3.1, VVR 3.1.1 and VVR 3.2. It has been reported as VERITAS Incident 100375, and is fixed in VERITAS Volume Manager (VxVM) 3.2 patch 3 and VxVM 3.5.

Supplemental Materials

SourceiTools
Value100375
DescriptionVVR: Replicas differ after Primary failover during resync


Legacy ID



250829


Article URL http://www.symantec.com/docs/TECH22239


Terms of use for this information are found in Legal Notices