Symantec logo

Secondary data volume error cleanup and recovery

If an I/O error occurs during access of a Secondary data volume, the data volume is automatically detached from the RVG and the RLINKs are disconnected. A subsequent attempt by the Primary to connect to the Secondary fails and a message that the Secondary volumes are stopped is displayed. The Primary is unaffected and writes continue to be logged into the SRL. After the Secondary data volume error is fixed and the data volume is started, the RLINKs automatically reconnect.

If there is no suitable Primary or Secondary checkpoint, detach the RLINKs on both the Primary and Secondary, and then synchronize the RLINKs. See Restoring the Secondary from online backup for details.

Recovery using a Secondary checkpoint

This section explains how to recover from a Secondary data volume error using a Secondary checkpoint.

On the Secondary (london):

  1. Repair the failed data volume. You need not dissociate the data volume if the problem can be fixed by repairing the underlying subdisks.
  2. Make sure that the data volume is started:

    # vxvol -g hrdg start hr_dv01

  3. Restore data from the Secondary checkpoint backup to all the volumes. If all volumes are restored from backup, the Secondary will remain consistent during the synchronization. Restore the RLINK by issuing the following command:

    # vxrlink -g hrdg -c sec_chkpt restore rlk_seattle_hr_rvg

Cleanup using a Primary checkpoint

On the Secondary (london):

  1. Repair the failed data volume as above. Be sure that the data volume is started before proceeding:

    # vxvol -g hrdg start hr_dv01

  2. Detach the RLINK to enable writing to the Secondary data volumes:

    # vxrlink -g hrdg det rlk_seattle_hr_rvg

  3. Restore data from the Primary checkpoint backup to all data volumes. Unlike restoration from a Secondary checkpoint, the Primary checkpoint data must be loaded onto all Secondary data volumes, not just the failed volume. If a usable Primary checkpoint does not already exist, make a new checkpoint. For details, see Example—Synchronizing the Secondary using block-level backup.
  4. Reattach the RLINK.

    # vxrlink -g hrdg att rlk_seattle_hr_rvg

On the Primary (seattle):

Detach the RLINK and then reattach it from the Primary checkpoint using the following commands:

# vxrlink -g hrdg det rlk_london_hr_rvg

# vxrlink -g hrdg -c primary_checkpoint att rlk_london_hr_rvg