Creating an SVM

You must create an SVM to serve data to clients.

Before you begin

Steps

  1. Determine which aggregates are candidates for containing the SVM root volume. storage aggregate show -has-mroot false
    Example
    storage aggregate show -has-mroot false
    Aggregate     Size Available Used% State   #Vols  Nodes  RAID Status
    --------- -------- --------- ----- ------- ------ ------ ------------
    aggr1      239.0GB   229.8GB    4% online       4 node1  raid_dp,
                                                                normal
    aggr2      239.0GB   235.9GB    1% online       2 node2  raid_dp,
                                                                normal
    aggr3      478.1GB   465.2GB    3% online       1 node2  raid_dp,
                                                                normal

    The best practice is to use a separate aggregate for SVM root volumes. You should not create a root volume on an aggregate that contains data volumes.

    You must choose an aggregate that has at least 1 GB of free space to contain the root volume. If you intend to configure NAS auditing on the SVM, you must have a minimum of 3 GB of extra free space on the root aggregate, with the extra space being used to create the auditing staging volume when auditing is enabled.

    Note: If NAS auditing is already enabled on an existing SVM, the aggregate's staging volume is created immediately after aggregate creation is successfully completed.
  2. Record the name of the aggregate on which you want to create the SVM root volume.
  3. If you plan on specifying a language when you create the SVM and do not know the value to use, identify and record the value of the language you want to specify: vserver create -language ?
  4. If you plan on specifying a Snapshot policy when you create the SVM and do not know the name of the policy, list the available policies and identify and record the name of the Snapshot policy you want to use: volume snapshot policy show -vserver vserver_name
  5. If you plan on specifying a quota policy when you create the SVM and do not know the name of the policy, list the available policies and identify and record the name of the quota policy you want to use: volume quota policy show -vserver vserver_name
  6. Create an SVM: vserver create -vserver vserver_name -aggregate aggregate_name -rootvolume root_volume_name -rootvolume-security-style {unix|ntfs|mixed} [-ipspace IPspace_name] [-language language] [-snapshot-policy snapshot_policy_name] [-quota-policy quota_policy_name] [-comment comment]
    Example
    vserver create -vserver vs1 -aggregate aggr3 -rootvolume vs1_root -rootvolume-security-style ntfs -ipspace ipspace1 -language en_US.UTF-8
    [Job 72] Job succeeded:                 Vserver creation completed
  7. Verify that the SVM configuration is correct.
    Example
    vserver show -vserver vs1
                                       Vserver: vs1
                                  Vserver Type: data
                               Vserver Subtype: default
                                  Vserver UUID: 11111111-1111-1111-1111-111111111111
                                   Root Volume: vs1_root
                                     Aggregate: aggr3
                                    NIS Domain: -
                    Root Volume Security Style: ntfs
                                   LDAP Client: -
                  Default Volume Language Code: en_US.UTF-8
                               Snapshot Policy: default
                                       Comment:
                                  Quota Policy: default
                   List of Aggregates Assigned: -
    Limit on Maximum Number of Volumes allowed: unlimited
                           Vserver Admin State: running
                     Vserver Operational State: running
      Vserver Operational State Stopped Reason: -
                             Allowed Protocols: nfs, cifs, ndmp
                          Disallowed Protocols: fcp, iscsi
               Is Vserver with Infinite Volume: false
                              QoS Policy Group: -
                                   Config Lock: false
                                  IPspace Name: ipspace1
                          Is Vserver Protected: false

    In this example, the command creates the SVM named "vs1" in IPspace "ipspace1". The root volume is named "vs1_root" and is created on aggr3 with NTFS security style.