Managing storage for ONTAP clusters
Contributors Download PDF of this page
After you discover your ONTAP cluster from Cloud Manager, you can open the working environment to provision and manage storage.
Creating volumes for ONTAP clusters
Cloud Manager enables you to provision NFS, CIFS, and iSCSI volumes on ONTAP clusters.
A Cloud Manager feature called "templates" enables you to create volumes that are optimized for the workload requirements for certain applications; such as databases or streaming services. If your organization has created volume templates that you should use, follow these steps.
The data protocols must be set up on the cluster using System Manager or the CLI.
You can create volumes on existing aggregates. You can’t create new aggregates from Cloud Manager.
On the Canvas page, double-click the name of the ONTAP cluster on which you want to provision volumes.
Click Add New Volume.
On the Create New Volume page, enter details for the volume, and then click Create.
Some of the fields in this page are self-explanatory. The following table describes fields for which you might need guidance:
The maximum size that you can enter largely depends on whether you enable thin provisioning, which enables you to create a volume that is bigger than the physical storage currently available to it.
A Snapshot copy policy specifies the frequency and number of automatically created NetApp Snapshot copies. A NetApp Snapshot copy is a point-in-time file system image that has no performance impact and requires minimal storage. You can choose the default policy or none. You might choose none for transient data: for example, tempdb for Microsoft SQL Server.
Access control (for NFS only)
An export policy defines the clients in the subnet that can access the volume. By default, Cloud Manager enters a value that provides access to all instances in the subnet.
Permissions and Users / Groups (for CIFS only)
These fields enable you to control the level of access to a share for users and groups (also called access control lists or ACLs). You can specify local or domain Windows users or groups, or UNIX users or groups. If you specify a domain Windows user name, you must include the user’s domain using the format domain\username.
Initiator group and IQN (for iSCSI only)
iSCSI storage targets are called LUNs (logical units) and are presented to hosts as standard block devices.
Initiator groups are tables of iSCSI host node names and control which initiators have access to which LUNs.
iSCSI targets connect to the network through standard Ethernet network adapters (NICs), TCP offload engine (TOE) cards with software initiators, converged network adapters (CNAs) or dedicated host bust adapters (HBAs) and are identified by iSCSI qualified names (IQNs).
When you create an iSCSI volume, Cloud Manager automatically creates a LUN for you. We’ve made it simple by creating just one LUN per volume, so there’s no management involved. After you create the volume, select it, click Target IQN, and then use the IQN to connect to the LUN from your hosts.
Usage profiles define the NetApp storage efficiency features that are enabled for a volume.
Creating volumes from templates
If your organization has created on-premises ONTAP volume templates so you can deploy volumes that are optimized for the workload requirements for certain applications, follow the steps in this section.
The template should make your job easier because certain volume parameters will already be defined in the template, such as disk type, size, protocol, snapshot policy, and more. When a parameter is already predefined, you can just skip to the next volume parameter.
|You can only create NFS or CIFS volumes when using templates.|
On the Canvas page, click the name of the on-premises ONTAP system on which you want to provision a volume.
Click > Add Volume From Template.
In the Select Template page, select the template that you want to use to create the volume and click Next.
The Define Parameters page is displayed.
Note: You can click the checkbox Show read-only parameters to show all the fields that have been locked by the template if you want to see the values for those parameters. By default these predefined fields are hidden and only the fields you need to complete are shown.
In the Context area, the Working Environment is filled in with the name of the working environment you started with. You need to select the Storage VM and Aggregate where the volume will be created.
Add values for all of the parameters that are not hard-coded from the template. See creating volumes for details about all the parameters you need to complete to deploy an on-prem ONTAP volume.
Click Run Template after you have defined all the parameters needed for this volume.
Cloud Manager provisions the volume and displays a page so that you can see the progress.
Then the new volume is added to the working environment.
Additionally, if any secondary action is implemented in the template, for example, enabling Cloud Backup on the volume, that action is also performed.
If you provisioned a CIFS share, give users or groups permissions to the files and folders and verify that those users can access the share and create a file.
You can replicate data between Cloud Volumes ONTAP systems and ONTAP clusters by choosing a one-time data replication, which can help you move data to and from the cloud, or a recurring schedule, which can help with disaster recovery or long-term retention.
Backing up data
You can back up data from your on-premises ONTAP system to low-cost object storage in the cloud by using the Cloud Manager Cloud Backup service. This service provides backup and restore capabilities for protection and long-term archive of your cloud data.
Tiering data to the cloud
Extend your data center to the cloud by automatically tiering inactive data from ONTAP clusters to object storage.