Table of ContentsView in Frames

Recovering a lost source FlexVol volume from a mirror

You might be able to use a load-sharing mirror to recover a source volume that is not accessible. This might be a good solution if you lose a source volume because a component failed, such as a shelf or port failure.

About this task

Step

  1. Use the snapmirror promote command to make a mirror a read-write volume that replaces the source read-write volume.
    Example
    The following example recovers a lost source volume from the load-sharing mirror named dept_eng_ls_mirror3 on an SVM named vs0 and a cluster named cluster1:
    cluster1::> snapmirror promote -destination-path 
    cluster1://vs0/dept_eng_ls_mirror3 -source-path 
    cluster1://vs0/eng
    Data ONTAP makes the destination volume of the mirror a read-write volume, destroys the original read-write volume if it is accessible, and redirects mirrors and clients that accessed the original read-write volume to the new read-write volume.
    Note: The recovered source volume might not have all of the data that the original source volume had because the SnapMirror relationship for load-sharing and data protection mirrors is a scheduled, asynchronous update and the update might not have occurred recently.