Table of ContentsView in Frames

Planning to create SVMs

You must understand the various aspects of SVMs that help you plan the SVM setup process. You must also understand the purpose for creating the SVM and understand details such as the type of volume the SVM should contain, the environment for data access, and network segregation.

SVMs for data access

You must create one or more SVMs to serve data from the cluster. SVMs can contain either one or more FlexVol Volumes or a single Infinite Volume to serve data to the clients.

You can also use OnCommand System Manager to create and configure SVMs with FlexVol volumes and SVMs with Infinite Volume.

Clustered Data ONTAP 8.3 Cluster Management Using OnCommand System Manager

You must understand the following SVM attributes when creating SVMs with FlexVol volumes for data access:

SVM attributes Possible values Description
SVM subtype default Data SVMs that are created for data access must have the subtype option set to default.
Volumes FlexVol volumes The -is-repository option must be set to false, which is the default value.
Protocols NFS, CIFS, iSCSI, and FC Data SVMs can serve data to NAS clients and SAN hosts simultaneously.
Root volume security style
  • mixed for NFS and CIFS
  • ntfs for CIFS
  • unix for NFS, iSCSI and FC
Based on the clients, you can select the appropriate security style for the SVM root volume.
IPspace Any available IPspace

IPspace defines a secured dedicated network path for each SVM.

You can segregate the network for the SVM by assigning the IPspace when creating the SVM.

You must understand the following SVM attributes when creating SVMs with Infinite Volume for data access:

SVM attributes Possible values Description
SVM subtype default Data SVMs that are created for data access must have the subtype option set to default.
Volumes Infinite Volume The -is-repository option must be set to true. The default value is false.
Protocols
  • NFS

    NFSv3, pNFS, and NFSv4.1 are supported.

  • CIFS

    SMB 1.0 is supported.

Data SVMs can serve data to NAS clients only.
Root volume security style
  • mixed for NFS and CIFS
  • ntfs for CIFS
  • unix for NFS
Based on the clients, you can select the appropriate security style for the SVM root volume.
IPspace Any available IPspace

IPspace defines a secured dedicated network path for each SVM.

You can segregate the network for the SVM by assigning the IPspace when creating the SVM.

SVMs for MetroCluster configuration

You can create source and destination Storage Virtual Machines (SVMs) for a MetroCluster configuration for providing synchronous disaster recovery and high availability of data.

Note: Only SVMs with FlexVol volumes are supported for a MetroCluster configuration.

You must understand the following SVM attributes when creating SVMs for the MetroCluster configuration:

SVM attributes Possible values Description
SVM subtype sync-source and sync-destination Source and destination SVMs that are created for a MetroCluster configuration have the subtype option set to sync-source and sync-destination , respectively.
Volumes FlexVol volumes You do not have to specify the -is-repository option because the default value is false.
Protocols NFS, CIFS, iSCSI, and FC Source and destination SVMs support all the protocols.
Root volume security style
  • mixed for NFS and CIFS
  • ntfs for CIFS
  • unix for NFS, iSCSI, and FC
The root volumes of the source and destination SVMs have an identical security style.
IPspace Any available IPspace

IPspace defines a secured dedicated network path for each SVM.

You can segregate the network for the SVM by assigning the IPspace when creating the SVM.

Source and destination SVMs must belong to IPspaces with the same name.