Table of ContentsView in Frames

Restoring a cluster configuration from an existing configuration

You re-create the cluster using the cluster configuration that you chose and made available to the recovering node, and then rejoin each additional node to the new cluster.

About this task

You should only perform this task to recover from a disaster that resulted in the loss of the cluster's configuration.

Steps

  1. On the recovering node, use the system configuration recovery cluster recreate command at the advanced privilege level to re-create the cluster.

    Example

    This example re-creates the cluster using the configuration information stored on the recovering node.

    cluster1::*>system configuration recovery cluster recreate -from node
    
    Warning: This command will destroy your existing cluster. It will
             rebuild a new single-node cluster consisting of this node
             and its current configuration. This feature should only be
             used to recover from a disaster. Do not perform any other
             recovery operations while this operation is in progress.
    Do you want to continue? {y|n}: y
    

    A new cluster is created, with a new UUID, on the recovering node.

  2. Use the cluster identity show command to verify that the recovering node has a different UUID than the other nodes.
  3. For each node that needs to be joined to the re-created cluster, do the following:
    1. From a healthy node on the re-created cluster, use the system configuration recovery cluster rejoin command at the advanced privilege level to rejoin the target node to the cluster.

      Example

      This example rejoins the target node (node2) to the re-created cluster.

      cluster1::*> system configuration recovery cluster rejoin -node node2
      
      Warning: This command will rejoin node "node2" into the local
               cluster, potentially overwriting critical cluster
               configuration files. This command should only be used
               to recover from a disaster. Do not perform any other
               recovery operations while this operation is in progress.
               This command will cause node "node2" to reboot.
      Do you want to continue? {y|n}: y
      

      The target node reboots and then joins the cluster.

    2. Use the cluster show command with the -eligibility parameter to verify that the target node is healthy and has formed quorum with the rest of the nodes in the cluster.

      The target node must rejoin the re-created cluster before you can rejoin another node.

After you finish

If the cluster has SnapMirror peer relationships, then you need to re-create the relationships. For more information, see the Clustered Data ONTAP Data Protection Guide.