SnapProtect - NetApp – Best Practices
Review the following best practices before using NetApp.
- It is recommended that you do not use the system volume (typically vol0) for user data.
- For any ONTAP version, it is recommended to provide the host name or IP address of a data port (e.g., e0A, e0B) during the NAS client or storage array configuration instead of using the management port (e.g., e0M). If you are using the management port, you must reassign the host name or IP address of the management port to a data port on the file server.
- To perform snapshots and backup to tape operations in parallel for the same data, use two backupsets.
Ensure that sufficient disk space is available for snapshot operations and the disk space used by snapshots is monitored frequently.
The space requirement for snapshots created during SnapProtect 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 another, 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
SnapProtect provides the full suite of capabilities for recovery regardless of the Volume to LUN relationship and ratio. However, a 1 to 1, Volume to LUN, relationship might simplify storage and application management. It is also best to ensure that each LUN resides within a Qtree in SnapMirror and SnapVault configurations. Thin Provisioned Volumes with LUNS make your storage provisioning and snapshot management flexible.
NetApp Schedule for Snapshots
Disable the native NetApp schedule for snapshots on volumes that SnapProtect manages. This ensures snapshot retention and storage use is in line with the policies defined within SnapProtect. Using the default setting for internal snapshot scheduling might cause contention problems if multiple calls to create snapshots occur at the same time. To change the default setting, you can clear the Scheduled checkbox for the volume from Filer View or System Manager.