Skip to main content

Creating SVMs for a MetroCluster configuration

You can create SVMs for a MetroCluster configuration to provide synchronous disaster recovery and high availability of data on clusters that are set up for a MetroCluster configuration.

Before you begin

  • The two clusters must be in a MetroCluster configuration.

  • Aggregates must be available and online in both clusters.

  • If required, IPspaces with the same names must be created on both clusters.

  • If one of the clusters forming the MetroCluster configuration is rebooted without utilizing a switchover, then the sync-source SVMs might come online as stopped rather than started.

About this task

When you create an SVM on one of the clusters in a MetroCluster configuration, the SVM is created as the source SVM, and the partner SVM is automatically created with the same name but with the -mc suffix on the partner cluster. If the SVM name contains a period, the -mc suffix is applied prior to the first period, for example, SVM-MC.DNS.NAME.

In a MetroCluster configuration, you can create 64 SVMs on a cluster. A MetroCluster configuration supports 128 SVMs.

  1. Use the vserver create command.

    The following example shows the SVM with the subtype sync-source on the local site and the SVM with the subtype sync-destination on the partner site:

    cluster_A::>vserver create -vserver vs4 -rootvolume vs4_root -aggregate aggr1 
    -rootvolume-security-style mixed
    [Job 196] Job succeeded:
    Vserver creation completed


    The SVM vs4 is created on the local site and the SVM vs4-mc is created on the partner site.
  2. View the newly created SVMs.
    • On the local cluster, verify the configuration state of SVMs: metrocluster vserver show

      The following example shows the partner SVMs and their configuration state:

      cluster_A::> metrocluster vserver show

                            Partner    Configuration
      Cluster     Vserver   Vserver    State
      ---------  --------  --------- -----------------
      cluster_A   vs4       vs4-mc     healthy
      cluster_B   vs1       vs1-mc     healthy

    • From the local and partner clusters, verify the state of the newly configured SVMs: vserver show command

      The following example displays the administrative and operational states of the SVMs:

      cluster_A::> vserver show

                                   Admin   Operational Root
      Vserver Type  Subtype        State   State       Volume     Aggregate
      ------- ----- -------       ------- --------    ----------- ----------
      vs4     data  sync-source   running   running    vs4_root   aggr1

      cluster_B::> vserver show

                                     Admin   Operational  Root
      Vserver Type  Subtype          State   State        Volume      Aggregate
      ------- ----- -------          ------  ---------    ----------- ----------
      vs4-mc  data  sync-destination running stopped      vs4_root    aggr1

    SVM creation might fail if any intermediate operations, such as root volume creation, fail and the SVM is in the initializing state. You must delete the SVM and re-create it.

Result

The SVMs for the MetroCluster configuration are created with a root volume size of 1 GB. The sync-source SVM is in the running state, and the sync-destination SVM is in the stopped state.