SnapDrive limitations for clustered Data ONTAP
Contributors Download PDF of this page
Some SnapDrive features and operations are not supported for clustered Data ONTAP.
Storage provisioning and Snapshot management operations are not supported on the Vserver’s root volume.
Operations on file specification or LUNs that span Data ONTAP operating in 7-Mode and storage systems running on clustered Data ONTAP are not supported.
The symbolic links that reside inside a mount point are not supported.
Aggregates that contain Vserver volumes must be assigned to the Vserver’s aggregate list to configure the Vserver and execute SnapDrive operations.
SnapDrive for UNIX does not support migration of the Vserver because it is not supported by clustered Data ONTAP.
Snap connect operation with the
-readonlyoption mounts only the
.snapshotdirectory on the host and does not create the clone volume.
In clustered Data ONTAP, the export policy is defined only at the volume level and not at the directory level. Therefore, the
.snapshotdirectory cannot be exported to the secondary host (the host that does not have the export permission on the parent volume).
SnapDrive for UNIX does not support volume-based SnapRestore (VBSR) operations from a Snapshot copy created prior to the base Snapshot copy, when the volume is in a SnapMirror or SnapVault operation.
SnapDrive for UNIX does not support the
snapdeleteoperation of the Snapshot copy created before SnapVault update, when the volume is in SnapVault (XDP) relationship.