Considerations when working with Snapshot copies
Contributors Download PDF of this page
There are certain considerations that you should keep in mind when using a Snapshot copy, such as the fact that SnapDrive for UNIX works only with Snapshot copies that it creates, or that Snapshot copies are automatically replicated from the storage system to the host, and so on.
When working with Snapshot operations, you should consider the following:
SnapDrive for UNIX works only with Snapshot copies that it creates.
It cannot restore Snapshot copies that it did not create.
When you create a Snapshot copy on a destination storage system, the Snapshot copy is automatically replicated from the source storage system on which it is created to the destination storage system.
SnapDrive for UNIX enables you to restore the Snapshot copy on the destination storage system as well.
Connecting to the originating host occurs when you use the
snapdrive snap connectcommand to connect to a Snapshot copy at a new location on the same host where it was last connected (or is still connected).
Snapshot support for storage entities spanning multiple storage system volumes or multiple storage systems is limited on configurations that do not allow a freeze operation in the software stack.
When you export the volume through the NFS protocol, you must set the Anonymous User ID option to 0 for the SnapDrive for UNIX commands to work.
When there are two JFS file systems (JFS and JFS2) in a single disk group, SnapDrive for UNIX supports operations only for the JFS2 file system.
SnapDrive for UNIX enables you to create Snapshot copies of a concurrent volume group, and to clone or restore using the same properties.
A Single-File SnapRestore (SFSR) operation followed immediately by the creation of a Snapshot copy fails.
You must retry the operation after some time passes. For more information, see the Clustered Data ONTAP Logical Storage Management Guide.