Guidelines for connecting Snapshot copies
-
PDF of this doc site
-
Administration for Linux
- Role-based access control in SnapDrive for UNIX
-
Installation and Administration for Solaris
- Role-based access control in SnapDrive for UNIX
- Creating and using Snapshot copies in SnapDrive for UNIX
-
Installation and Administration for IBM AIX
- Role-based access control in SnapDrive for UNIX
-
Administration for Linux
Collection of separate PDF docs
Creating your file...
Follow the guidelines when connecting to Snapshot copies.
-
The
snapdrive snap connect
command works only with Snapshot copies created in SnapDrive 4.2 for UNIX. -
On an originating host, SnapDrive for UNIX supports connecting and restoring Snapshot copies that are created by previous versions of SnapDrive for UNIX.
-
For read and write access to NFS directory trees, the
snapdrive snap connect
command uses the Data ONTAP FlexVol volume feature, and therefore requires Data ONTAP 7.3 or later. Configurations with Data ONTAP 7.1 can connect NFS files or directory trees, but are provided with read-only access. -
If you set the
enable-split-clone
configuration variable value to “on” or “sync” during the Snapshot connect operation and “off” during the Snapshot disconnect operation, SnapDrive for UNIX does not delete the original volume or LUN that is present in the Snapshot copy. -
You have to set the value of Data ONTAP 7.2.2 configuration option vfiler.
vol_clone_zapi_allow
to “on” to connect to a Snapshot copy of a volume or LUN in a vFiler unit. -
The Snapshot connect operation is not supported on the hosts having different host configurations.
-
The
snapdrive snap connect
command used to connect to a root volume of a physical storage system or a vFiler unit fails because Data ONTAP does not allow cloning of a root volume.