< Previous  | TOC | Index | Next  >

Secondary SRL header error cleanup and recovery

An SRL header failure on the Secondary puts the Secondary RVG into the fail state, and sets the RLINK state to the pause state on both the Primary and Secondary. Because information about data volume errors is kept in the SRL header, the correct state of data volumes is not guaranteed in all cases. If a Secondary SRL header failure occurs during normal operation and is noticed before a reboot occurs, any data volumes that also failed will have a state of detached. If the system is rebooted before the vxprint command shows the volumes to be in the detached state, the status of any failed data volumes may be lost. Both these cases involve multiple errors and are unlikely, but it is important to understand that the state of Secondary data volumes can be suspect with this type of error.

1. Dissociate the SRL volume.

   # vxvol -g hrdg dis hr_srl

2. Repair the SRL volume. Even if the problem can be fixed by repairing the underlying subdisks, the SRL volume must still be dissociated and re-associated to initialize the SRL header.
3. Start the SRL volume. Then, re-associate it.

   # vxvol -g hrdg start hr_srl

   # vxvol -g hrdg aslog hr_rvg hr_srl

4. Start the RVG.

   # vxrvg -g hrdg start hr_rvg

5. If the integrity of the data volumes is not suspect, just resume the RLINK.

   # vxrlink -g hrdg resume rlk_seattle_hr_rvg

   OR

   If the integrity of the data volumes is suspect, and a Secondary checkpoint backup is available, restore from the Secondary checkpoint.

   # vxrlink -g hrdg det rlk_seattle_hr_rvg

   # vxrlink -g hrdg -f att rlk_seattle_hr_rvg

   # vxrlink -g hrdg -w pause rlk_seattle_hr_rvg

   Restore the Secondary checkpoint backup data on to the data volumes.

   # vxrlink -g hrdg -c secondary_checkpoint restore \

   rlk_seattle_hr_rvg

   OR

   If the integrity of the data volumes is suspect and no Secondary checkpoint is available, synchronize the Secondary using a block-level backup and Primary checkpoint (see Example—Synchronizing the Secondary using block-level backup) or automatic synchronization.

   # vxrlink -g hrdg det rlk_seattle_hr_rvg

   On the Secondary, restore the Primary checkpoint backup data to the data volumes.

   # vxrlink -g hrdg -f att rlk_seattle_hr_rvg

   On the Primary (seattle):

   # vxrlink -g hrdg -c primary_checkpoint att \

   rlk_london_hr_rvg