# Best Practices for the NetApp Storage Array

Review the following best practices before using the NetApp storage array.

## General

- Do not use the system volume (typically, vol0) for user data.

- For any ONTAP version, when you configure a NAS client or when you configure a storage array, provide the host name or IP address of a data port (for example, e0A, or e0B), instead of using the management port (for example, e0M).

  Note

  A NAS client configured with an NDMP agent typically uses port 10000 for the NDMP control connection. If the file server uses a different port number, you must configure the NDMP protocol under the NAS client to use that port number. For more information on port requirements for a NAS client, see Port Requirements for Commvault.

- To perform snapshots and backup to tape operations in parallel for the same data, use two backupsets.

- Do not use ONTAP 8.1.2 for performing IntelliSnap backup of NetApp LUNs, due to slower performance when reading from a mounted LUN. Use a later ONTAP version, such as 8.1.3. Consult NetApp for recommendations on the ONTAP version that is the best for your environment.

## NetApp Schedules for Snapshots

Disable the native NetApp schedule for snapshots on volumes that Commvault manages. This ensures that the snapshot retention and the storage use are in line with the policies defined within Commvault. If multiple calls to create snapshots occur at the same time, then using the default setting for internal snapshot scheduling might cause contention problems. To change the default settings, you can clear the Scheduled check box for the volume from Filer View or System Manager.

## Space Utilization

Ensure that sufficient disk space is available for snapshot operations and frequently monitor the disk space used by snapshots.
The space requirement for snapshots created during IntelliSnap backup can vary based on your environment. The space utilization is dependent on the number of snapshots created and the retention period defined for the snapshots.

When planning for snapshots, group LUNs according to their rate of change. For example, group LUNs with a high rate of change in the same volume and group LUNs with a low rate of change in a separate volume. When calculating the size of volumes, use the rate of change to determine the amount of space necessary for snapshots.

## Volume to LUN

Regardless of the volume-to-LUN relationship and ratio, IntelliSnap provides the full suite of capabilities for recovery. However, a 1-to-1 relationship might simplify storage and application management. In SnapMirror and SnapVault configurations, ensure that each LUN resides within a Qtree. Thin provisioned volumes with LUNs make your storage provisioning and snapshot management flexible.

×

Loading...