Snap disconnect operation fails to delete cloned volume
Contributors
Suggest changes
-
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...
This may take a few minutes. Thanks for your patience.
Your file is ready
In some cases, snapdrive snap disconnect
operation fails to delete cloned volume and the error message does not look SnapDrive-generated
appears.
The workaround for the problem is to revert to the original name of the Snapshot copy, and ensure that the bypass-snapdrive-clone-generated-check
is set to on
in the snapdrive.conf
file.