Skip to main content

Promote a load-sharing mirror with ONTAP

Contributors netapp-aaron-holt netapp-aherbin netapp-dbagwell netapp-lenida

If a root volume is permanently unavailable, you can promote the load-sharing mirror (LSM) volume to provide write access to root volume data.

Before you begin

You must use advanced privilege level commands for this task.

Steps
  1. Change to advanced privilege level:

    set -privilege advanced
    Cli
  2. Promote an LSM volume:

    You must replace the variables in angle brackets with the required values before running this command.

    snapmirror promote -destination-path <SVM:volume>
    Cli

    Learn more about snapmirror promote in the ONTAP command reference.

    The following example promotes the volume svm1_m2 as the new SVM root volume:

    cluster_src::*> snapmirror promote -destination-path svm1:svm1_m2
    
    Warning: Promote will delete the offline read-write volume
             cluster_src://svm1/svm1_root and replace it with
             cluster_src://svm1/svm1_m2. Because the volume is offline,
             it is not possible to determine whether this promote will
             affect other relationships associated with this source.
    Do you want to continue? {y|n}: y

    Enter y. ONTAP makes the LSM volume a read/write volume, and deletes the original root volume if it is accessible.

    Note

    The promoted root volume might not have all of the data that was in the original root volume if the last update did not occur recently.

  3. Return to admin privilege level:

    set -privilege admin
    Cli
  4. Rename the promoted volume following the naming convention you used for the root volume:

    You must replace the variables in angle brackets with the required values before running this command.

    volume rename -vserver <SVM> -volume <volume> -newname <new_name>
    Cli

    The following example renames the promoted volume svm1_m2 with the name svm1_root:

    cluster_src::> volume rename -vserver svm11 -volume svm1_m2 -newname svm1_root
  5. Protect the renamed root volume, as described in step 3 through step 4 in Creating and initializing load-sharing mirror relationships.