vserver create

Create a Vserver

Availability: This command is available to cluster administrators at the admin privilege level.


The vserver create command creates a Vserver.


-vserver <vserver> - Vserver
This specifies the name of the Vserver that is to be created. Use a fully qualified domain name (FQDN) - for example, "data.example.com" - for the Vserver to ensure unique Vserver names across cluster leagues.
Note: Maximum number of characters supported is 47, and 41 for a Vserver with subtype "sync-source". "all" is a reserved name and must not be used as a Vserver name.
[-subtype <vserver subtype>] - Vserver Subtype
This specifies the subtype of the Vserver being created. Possible values are:
  • default - For default data Vservers
  • dp-destination - For Data Protection destination Vservers
  • sync-source - For MetroCluster source Vservers
  • sync-destination - For MetroCluster destination Vservers
-rootvolume <volume name> - Root Volume
This specifies the name of the Vserver's root volume, which is created when the Vserver is created. The size of the Vserver's root volume is 1GB
-aggregate <aggregate name> - Aggregate
This specifies the storage aggregate that holds the Vserver's root volume.
  • Creating a root volume on the SnapLock aggregate is not supported.
  • Creating a root volume of sync-source Vserver on the unmirrored aggregate is not supported.
-rootvolume-security-style <security style> - Root Volume Security Style
This specifies the security style for the Vserver's root volume. Possible values include unix (for UNIX mode bits), ntfs (for CIFS ACLs), and mixed (for mixed NFS and CIFS access). Regardless of the security style, both NFS and CIFS clients can read from and write to the root volume. The unified security style, which applies only to Infinite Volumes, cannot be applied to a Vserver's root volume.
[-language <Language code>] - Default Volume Language Code
This optionally specifies the default language encoding setting for the Vserver and its volumes. The recommended format is to append .UTF-8 for the language encoding values. For example, for the en_US language, the recommended format is en_US.UTF-8. The default setting is C.UTF-8.
[-snapshot-policy <snapshot policy>] - Snapshot Policy
This optionally specifies the Snapshot policy for new volumes created on the Vserver. If no value is specified, the default Snapshot policy is used. You can use the -snapshot-policy parameter on the volume create or volume modify commands to set the Snapshot policy on a specific volume, regardless of its Vserver's Snapshot policy setting.
[-comment <text>] - Comment
This optionally specifies a comment for the Vserver.
[-quota-policy <text>] - Quota Policy
This optionally specifies a quota policy for the Vserver. This parameter is not supported on a Vserver with Infinite Volume.
[-is-repository {true|false}] - Is Vserver with Infinite Volume
This specifies that the Vserver will contain an Infinite Volume.
[-caching-policy <text>] - Caching Policy Name
This optionally specifies the caching policy to apply to the Vserver. A caching policy defines how the system caches this volume's data in Flash Cache modules. If a caching policy is not assigned to this Vserver, the system uses the default cluster-wide policy. The available caching policies are:
  • none - Does not cache any user data or metadata blocks.
  • auto - Read caches all metadata and randomly read user data blocks, and write caches all randomly overwritten user data blocks.
  • meta - Read caches only metadata blocks.
  • random_read - Read caches all metadata and randomly read user data blocks.
  • random_read_write - Read caches all metadata, randomly read and randomly written user data blocks.
  • all_read - Read caches all metadata, randomly read, and sequentially read user data blocks.
  • all_read_random_write - Read caches all metadata, randomly read, sequentially read, and randomly written user data.
  • all - Read caches all data blocks read and written. It does not do any write caching.
Default caching-policy is auto.
[-ipspace <IPspace>] - IPspace Name
This optionally specifies the IPspace the Vserver will be assigned to. If left unspecified, the Vserver will be assigned to the default IPspace.
[-foreground {true|false}] - Foreground Process
This optionally specifies whether the Vserver create operation can be executed in the background. If nothing is specified, by default the Vserver create operation is executed in the foreground.


The following example creates a Vserver named vs0.example.com in the IPspace ipspace123. The Vserver's root volume is named root_vs0 and is located on aggregate aggr0. The Vserver uses NIS for network information, a file for name mapping information, and the language is U.S. English:
cluster1::> vserver create -vserver vs0.example.com -ipspace ipspace123 -rootvolume root_vs0 -aggregate aggr0
-language en_US.UTF-8 -rootvolume-security-style mixed