SnapProtect - SnapProtect for Open Systems C-Mode - Getting Started – NetApp
Install the following licenses:
- FCP and iSCSI licenses for features such as Fibre Channel and iSCSI protocols. Use the appropriate license for specific data types
- HTTP/HTTPS licenses on the destination NetApp file server for communication
- The NetApp license:
- NFS Server license for backup operations
- If you use SnapMirror, install the additional licenses:
- NetApp Snap Management license in the CommCell Console
- SnapMirror Primary and Secondary Licenses for disaster recovery operations
- For OnCommand Unified Manager, install the following licenses:
- Operations Manager
- Provisioning Manager
- Install NetApp filers C-Mode ONTAP 8.3 including subversions, 9.0, or 9.1
- Install OnCommand Unified Manager 6.3P1, 6.4P1, 7.0 or 7.1. Configure OnCommand Unified Manager and its components
- Enable Storage Virtual machines used with SPOS C-Mode with NFS protocol version 3.0. Later versions of the NFS protocol are not supported
- If you plan to use proxy and client computers to mount snapshots, configure the iSCSI initiator on the client and proxy computers to access the snapshot device. If you plan to use only the proxy computer to mount snapshots, you can configure the iSCSI initiator on the proxy only.
- Install SnapProtect 11.0 SP2 or later
- Install MediaAgent on any client computer whose data will be backed up using SPOS C-Mode
- Install Linux LVM, or Veritas VxvM on UNIX clients. The source for the backup must be from a device that is either a Linux LVM, or a Veritas VxvM volume or a partitioned volume.
- For partitioned volumes, the cvbf cache location must be on different volume than the volume to back up
- For Linux, to back up the root partitioned volume, set the cvbf cache location to a volume that will not be part of the snapshot. Edit the registry key /etc/CommVaultRegistry/Galaxy/Instance001/FileSystemAgent/sCVBFSNAPPART to a value that is different from the default /opt/snapprotect/CVBF/cache.
Storage Space Requirements
UNIX - Space Requirements for Volume Group
You must have 10% of the volume size with free space to avoid snapshot failures. To increase the COW cache size, configure the nSnapCowSizeMB additional setting. For instructions on adding the additional setting, see Add or Modify an Additional Setting.
Windows - VSS Storage Space for Snapshot
You must set the initial storage space (minimum storage space) using the registry key MinDiffAreaFileSize. No maximum storage space is required. For more information on MinDiffAreaFileSize and requirements for specific Windows versions, refer to the Microsoft Windows Dev Center article Registry Keys and Values for Backup and Restore.
- One single installation of SPOS C-Mode is supported.
- Install the Workflow Engine. See more information about Workflow Engine.
- NFS server must be running on the vServer chosen to replicate data to.
- The vServer must have at least one logical interface (LIF) that has the data-protocol set to NFS.
- Disable NFS mount root only and NFS root only on the storage virtual machine, by running the command nfs modify
For example, the command below disables NFS mount root only and NFS root only in a storage virtual machine nfs_vs:nfs modify -mount-rootonly disabled -nfs-rootonly disabled -vserver nfs_vs
- Enable read-write access to SPOS C-Mode clients to the export policy associated with the root volume of the selected Storage Virtual Machine.
- Define a rule that provides read-write access to a client running a SPOS job in the export policy associated with the root volume of the vServer where data is replicated to. You can choose this vServer from the storage policy copy properties.
- Enable the iSCSI interface for LUN mounts on the vServer