Requirements for using SnapMirror with SnapDrive

Before you can use SnapMirror with SnapDrive for Windows, your system must meet several requirements.

SnapMirror must be licensed on the source and destination storage systems. For information on how to license and set up SnapMirror, see the Data ONTAP Data Protection Online Backup and Recovery Guide.
Note: For Cluster-Mode, you can perform a SnapMirror operation only when you provide Cserver credentials in the transport protocol settings.
Depending on the LUN protocols you are using, enable the iSCSI and FC licenses on the destination storage systems to enable LUN connect and LUN management operations.
You must manually create and initialize a plex between the source and destination volumes, but you must not create a SnapMirror replication schedule.
When setting up SnapMirror on your storage system, you can avoid schedule conflicts with SnapDrive by setting the replication schedule on the storage system to “- - - -”, which disables any scheduled transfers. When you set the replication schedule, ensure that the destination volume is in a restricted state. See the Data ONTAP Data Protection Online Backup and Recovery Guide for additional details.
You must create your SnapMirror relationship using storage system names (either the fully qualified DNS name or the storage system name alone), and the network interface to be used for SnapMirror transfers (for example, storage1-e0), not IP addresses.
If you are using the optional MultiStore feature of the Data ONTAP software to create virtual storage systems (vFiler units), you must create your SnapMirror relationship on the vFiler unit, not on the physical storage system.
The system must contain one or more SnapMirror source volumes hosting LUNs.
The system must contain one or more SnapMirror destination volumes for each source volume.
Note: SnapDrive supports the use of SnapMirror at the volume level only; it does not support qtree-level SnapMirror operations.
The destination volume must be at least as large as the source volume.
The Windows domain account used by the SnapDrive service must be a member of the local BUILTIN\administrators group and must have management access to both the source and destination storage systems.
The Windows domain account used to administer SnapDrive must have full access to the Windows domain to which both the source and destination storage systems belong.
The source and destination storage systems must be configured to grant root access to the Windows domain account used by the SnapDrive service. That is, the wafl.map_nt_admin_priv_to_root option must be set to On. For information about enabling storage system options, see your Data ONTAP documentation.
If you want to use a Windows host to access the replicated LUNs on the destination volume, the destination storage system must have at least one LUN access protocol licensed (iSCSI or FC).
A TCP/IP connection must exist between the source storage system and the destination storage system.
The SnapDrive service can perform one task at a time. Therefore, if you are scheduling multiple tasks on a host, ensure that you do not schedule these tasks to start at exactly the same time.
If multiple tasks are scheduled at the same time, the first will proceed, and SnapDrive will queue the others until the first task either succeeds or times out.

Note: SnapMirror cascaded configurations are not supported.