Request doc changes
Edit this page
Learn how to contributeMultipathing in SnapDrive for UNIX
SnapDrive for UNIX supports multipathing. SnapDrive for UNIX does not support the use of aliases for devices, created using the mknod and/or rendev commands.
-
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
-
-
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
- Home
- Release notes
-
Install and and Setup for Linux for Clustered Data ONTAP
-
Installation and Setup for Linux for Data ONTAP Operating in 7-Mode
-
Administration for Linux
-
Product overview
- Clustered Data ONTAP features available in SnapDrive for UNIX
- Support for Vserver
- Support for NetAppDataMotion for vFiler
-
Support for volume migration
- vFiler unit support issues
- Considerations for using SnapDrive for UNIX
-
Management of an LVM and raw entities
- How to manage Snapshot copies of LVM, raw devices, and NFS entities
- Security considerations
- Access permissions on a storage system
- Stack requirements
- Supported FC, iSCSI, or NFS configurations
- Limitations
- Limitations of LUNs managed by SnapDrive
- Limitations of RDM LUNs managed by SnapDrive
- SnapDrive limitations for clustered Data ONTAP
- Limitations for NFS files or directory trees
- Thin provisioning in SnapDrive for UNIX
- Volume managers on SnapDrive for UNIX
- New in this release
-
Understanding the SnapDrive for UNIX daemon
- What the Web service and daemon are
- Checking the status of the daemon
- Starting the SnapDrive for UNIX daemon
- Changing the default daemon password
-
Stopping the daemon
- Restarting the daemon
- Forcing daemon restart
- Secure daemon communication using HTTPS
- Generating self-signed certificates
- Generating a CA-signed certificate
-
Support for storage system rename
-
SnapDrive for UNIX configuration
-
Configuring SnapDrive for UNIX
- What the snapdrive.conf file is
- Configuration options and their default values
- What the SnapDrive configuration wizard does
- SnapDrive configuration wizard
- Some configuration commands
- Using the SnapDrive configuration wizard
- Setting values in the snapdrive.conf file
- Checking the version of SnapDrive for UNIX
-
Configuration information in SnapDrive for UNIX for guest operating system
-
Configuration information for Vserver
-
Host preparation for adding LUNs
-
Audit, recovery, and trace logging in SnapDrive for UNIX
-
What AutoSupport is
-
Support for multipath access in SnapDrive for UNIX
-
Thin provisioning in SnapDrive for UNIX
-
Multiple subnet configuration
- Automatic detection of host entities
-
What SnapDrive wizards are
-
Using port set in SnapDrive for UNIX
-
Configuring igroups
- Using Selective LUN Map in SnapDrive for UNIX
-
FlexClone volumes in SnapDrive for UNIX
-
-
Security features in SnapDrive for UNIX
-
Role-based access control in SnapDrive for UNIX
- What role-based access control (RBAC) in SnapDrive for UNIX is
- SnapDrive for UNIX and Operations Manager console interaction
-
Configuration of role-based access control in SnapDrive for UNIX
- SnapDrive commands and capabilities
- Preconfigured roles for ease of user role configuration
- Automatic storage system update on Operations Manager console
- Multiple Operations Manager console servers
- Operations Manager console unavailable
-
RBAC and storage operation examples
-
Storage provisioning in SnapDrive for UNIX
-
Storage operations in SnapDrive for UNIX
-
Storage creation with SnapDrive for UNIX
- Methods for creating storage
- Guidelines for the storage create operation
- Information required for the storage create operation
- Storage creation for LVM entities
- Storage creation for a file system that resides on a LUN
-
Storage partitioning scheme in Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SLES)
- Creating LUNs without host entities
- Creating a file system on a LUN and setting up the LUN automatically
- Creating a file system on a LUN and specifying the LUN
- Creating an LVM entity and setting up the LUN automatically
- Creating an LVM entity and specifying the LUN
-
Command to use to display available storage
-
Increase in storage size using SnapDrive for UNIX
-
The storage connect command
-
The storage disconnect command
- Methods for disconnecting storage
- Guidelines for the snapdrive storage disconnect command
- Tips for using the storage disconnect command
- Information required for using the snapdrive storage disconnect command
- Command syntax for disconnecting LUNs from the host
- Command syntax for disconnecting a file system created on a LUN from the host
- Command syntax for disconnecting LUNs and storage entities from the host
-
The storage delete command
-
-
Creating and using Snapshot copies in SnapDrive for UNIX
-
What Snapshot operations are in SnapDrive for UNIX
-
Snapshot copy operations
-
Snapshot copies information display
- Command to use to display Snapshot copy information
- Guidelines for displaying Snapshot copies
- Information required for using the snapdrive snap show or list commands
- Displaying Snapshot copies residing on a storage system
- Displaying Snapshot copies of a storage system volume
- Displaying a Snapshot copy
- Other ways to get Snapshot copy names
-
Snapshot copy rename
-
Restoring a Snapshot copy
- Command to use to restore Snapshot copies
-
Restoring Snapshot copies on a destination storage system
- Considerations for restoring a Snapshot copy
- Information required for using the snapdrive snap restore command
- Restoring a Snapshot copy
- Restoring a Snapshot copy from a different host
-
Volume-based SnapRestore
- What volume-based SnapRestore is
- Considerations for using volume-based SnapRestore
- Mandatory checks for volume-based SnapRestore
- Checks that can be overridden by the user
- Volume-based SnapRestore command
- Information about LUNs mapped to local or remote hosts
- Host filespec information for a particular volume
- Volume-based SnapRestore for space reservation
-
Connecting to a Snapshot copy
- How the snapdrive snap connect command works
-
Connecting Snapshot copies on mirrored storage systems
- Snapshot connect and Snapshot restore operations
- Guidelines for connecting Snapshot copies
- Information required for using the snapdrive snap connect command
- Connecting to a Snapshot copy that contains LUNs
- Connecting to a Snapshot copy of storage entities other than LUNs
- Connecting to Snapshot copies of shared storage entities other than LUNs
-
Splitting a volume clone or LUN clone
- Estimating the storage space to split a volume clone
- Estimating the storage space to split a LUN clone
- Estimating the storage space using a Snapshot copy
- Starting the volume clone or LUN clone split
- Viewing the status of a volume clone or LUN clone split
- Stopping the volume clone or LUN clone split operation
- Viewing the result of a clone split operation using job ID or file specification
-
Deleting a Snapshot copy
-
Disconnecting a Snapshot copy
- Using the Snapshot disconnect operation
-
Guidelines for disconnecting Snapshot copies
- Information required for using the snapdrive snap disconnect command
- Disconnecting Snapshot copy with LUNs and no storage entities
- Disconnecting Snapshot copy with storage entities
- Disconnecting Snapshot copies with shared storage entities
-
-
Data collection utility
-
Troubleshooting
-
Understanding error messages
-
Common error messages
- SnapDrive storage create command fails when multiple SAN paths are present but multipathing is disabled
- If a volume is deleted on the Vserver without unmounting the volume on the host system, the snapdrive storage show command displays the incorrect actual path
- Snap management operation fails in RHEL/OEL 5.x due to an issue with umount command
- Snap restore operation fails when you have nfsv3 and nfsv4 versions enabled in the host and storage system
- Snap disconnect operation fails to delete cloned volume
- SnapRestore and Snapconnect operations does not work in Linux after multipathing type migration
- SnapDrive for UNIX reports an error if iSCSI is not running
- Discrepancy in the error code message
- Data disappears when you add LUNs to a volume group
- SnapDrive command fails when the transport protocol connectivity fails
- Autodetection does not work with MPIO setup for an FS created over a raw LUN
- Connecting to a Snapshot copy fails
- Deleting LUNs with exported disk groups on Linux LVM2 fails
- LUN discovery fails due to iSCSI daemon limitation
- Commands appear blocked
- After each reboot snap connect yields "0001-680 Admin error: Host OS requires an update to internal data"
- SnapDrive errors out if libgcc_s.so.1 is not installed
- Error loading the /usr/lib/libqlsdm.so in HBA_LoadLibrary
- Restoring a file system from a Snapshot copy fails
- Snapshot restore operation fails to restore file system on raw LUN
- Snap connect operation fails
-
Standard exit status values
- Cleaning up the mapped RDM LUNs in the guest operating system and ESX server
- Volume-based SnapRestore check fails
- Snapshot create and delete operation fails
- Unable to create a Snapshot copy
- Unable to restore a Snapshot copy
- Unable to restart the daemon when host cannot communicate to the storage system
- Unable to start the daemon
- snapdrived start command fails
- SnapDrive commands sometimes result in mounting or unmounting file systems and modify system files
- Unable to select a storage stack
- snapdrived stop or snapdrived start command hangs
- SnapDrive for UNIX command displays could not check access error
- Mounting a FlexVol volume fails in NFS environment
- Receiving error iscsi64 snapdrive: 0001-666 FATAL error
- SnapDrive for UNIX incorrectly interprets the dollar sign
- SnapDrive for UNIX displays an error message after SUSE Linux Enterprise Server is upgraded from version 10 to 11
- SnapDrive for UNIX storage create command fails while discovering some mapped devices
- SnapDrive for UNIX commands fail with customized LD_LIBRARY_PATH
- SnapDrive operations fail in multiple subnet configuration
- SnapDrive for UNIX commands fail when environment variables are set using a command shell
- SnapDrive for UNIX does not automatically delete stale devices in UNIX
- SnapDrive fails to add newly mapped LUNs in RHEL 6.6 and later
- SnapDrive for UNIX operations fails due to improper multipath settings when aliased devices are used.
-
-
Command reference
-
-
Installation and Administration for Solaris
-
SnapDrive for UNIX overview
- What SnapDrive for UNIX does
- Features supported in SnapDrive for UNIX
- Operations performed on stand-alone UNIX systems
- Support for guest operating systems
- Operations supported on host clustered UNIX systems
- How SnapDrive for UNIX works on host clustered UNIX systems
- Support for Vserver
- vFiler unit support issues
- Considerations for using SnapDrive for UNIX
-
Management of VxVM and raw entities
- How to manage Snapshot copies of VxVM, raw devices, and NFS entities
- Security considerations
- Access permissions on a storage system
- Requirements for storage systems
- Stack requirements
- Supported FC, iSCSI, or NFS configurations
- Limitations
- Limitations of LUNs managed by SnapDrive
- Limitations of RDM LUNs managed by SnapDrive
- Support for NetAppDataMotion for vFiler
-
Support for volume migration
- What configuration checker is
- Limitations for NFS files or directory trees
- Thin provisioning in SnapDrive for UNIX
- Volume managers on SnapDrive for UNIX
- Host cluster environment for SnapDrive for UNIX
-
Preparing to install SnapDrive for UNIX
-
Hardware and software configuration
-
Preparing your storage system
-
Host preparation for installing SnapDrive for UNIX
-
Guest OS preparation for installing SnapDrive for UNIX
-
-
Installing or upgrading SnapDrive for UNIX
- Downloading and decompressing the software package
- Installing SnapDrive for UNIX on a Solaris host
- Setting up an SFRAC I/O fencing environment on a storage system
- Adding a node to a host cluster
- Removing a node from a host cluster
- Uninstalling SnapDrive for UNIX from a Solaris host
- Verifying the Veritas stack configuration
- Performing post-installation checks
-
Files installed by SnapDrive for UNIX
- Upgrade SnapDrive for UNIX to current version
-
Understanding the SnapDrive for UNIX daemon
- What the Web service and daemon are
- Checking the status of the daemon
- Starting the SnapDrive for UNIX daemon
- Changing the default daemon password
-
Stopping the daemon
- Restarting the daemon
- Forcing daemon restart
- Secure daemon communication using HTTPS
- Generating self-signed certificates
- Generating a CA-signed certificate
-
Verifying supported configurations
-
Support for storage system rename
-
Using port set in SnapDrive for UNIX
-
Configuring igroups
- Using Selective LUN Map in SnapDrive for UNIX
-
SnapDrive for UNIX configuration
-
Configuring SnapDrive for UNIX
- What the snapdrive.conf file is
- Configuration options and their default values
- What the SnapDrive configuration wizard does
- SnapDrive configuration wizard
- Some configuration commands
- Using the SnapDrive configuration wizard
- Setting values in the snapdrive.conf file
- Checking the version of SnapDrive for UNIX
-
Configuration information in SnapDrive for UNIX for guest operating system
-
Configuration information for Vserver
-
Host preparation for adding LUNs
-
Audit, recovery, and trace logging in SnapDrive for UNIX
-
What AutoSupport is
-
Support for multipath access in SnapDrive for UNIX
-
Thin provisioning in SnapDrive for UNIX
-
Multiple subnet configuration
- Automatic detection of host entities
-
What SnapDrive wizards are
-
-
Security features in SnapDrive for UNIX
-
Role-based access control in SnapDrive for UNIX
- What role-based access control (RBAC) in SnapDrive for UNIX is
- SnapDrive for UNIX and Operations Manager console interaction
-
Configuration of role-based access control in SnapDrive for UNIX
- SnapDrive commands and capabilities
- Preconfigured roles for ease of user role configuration
- Automatic storage system update on Operations Manager console
- Multiple Operations Manager console servers
- Operations Manager console unavailable
-
RBAC and storage operation examples
-
FlexClone volumes in SnapDrive for UNIX
-
Storage provisioning in SnapDrive for UNIX
-
Storage operations in SnapDrive for UNIX
-
Storage creation with SnapDrive for UNIX
- Methods for creating storage
-
Guidelines for the storage create operation
- Information required for the storage create operation
- Storage creation for VxVM entities
- Storage creation for a file system that resides on a LUN
- Creating LUNs without host entities
- Creating a file system on a LUN and setting up the LUN automatically
- Creating a file system on a LUN and specifying the LUN
- Creating a VxVM entity and setting up the LUN automatically
- Creating a VxVM entity and specifying the LUN
-
Command to use to display available storage
-
Increase in storage size using SnapDrive for UNIX
-
The storage connect command
-
The storage disconnect command
- Methods for disconnecting storage
-
Guidelines for the snapdrive storage disconnect command
- Tips for using the storage disconnect command
- Information required for using the snapdrive storage disconnect command
- Command syntax for disconnecting LUNs from the host
- Command syntax for disconnecting a file system created on a LUN from the host
- Command syntax for disconnecting LUNs and storage entities from the host
- Disable a node or a cluster from using shared resources
-
The storage delete command
-
-
Creating and using Snapshot copies in SnapDrive for UNIX
-
What Snapshot operations are in SnapDrive for UNIX
-
Snapshot copy operations
-
Snapshot copies information display
- Command to use to display Snapshot copy information
- Guidelines for displaying Snapshot copies
- Information required for using the snapdrive snap show or list commands
- Displaying Snapshot copies residing on a storage system
- Displaying Snapshot copies of a storage system volume
- Displaying a Snapshot copy
- Other ways to get Snapshot copy names
-
Snapshot copy rename
-
Restoring a Snapshot copy
- Command to use to restore Snapshot copies
-
Restoring Snapshot copies on a destination storage system
- Considerations for restoring a Snapshot copy
- Information required for using the snapdrive snap restore command
- Restoring a Snapshot copy
- Restoring a Snapshot copy from a different host
-
Volume-based SnapRestore
- What volume-based SnapRestore is
- Considerations for using volume-based SnapRestore
- Mandatory checks for volume-based SnapRestore
- Checks that can be overridden by the user
- Volume-based SnapRestore command
- Information about LUNs mapped to local or remote hosts
- Host filespec information for a particular volume
- Volume-based SnapRestore for space reservation
-
Connecting to a Snapshot copy
- How the snapdrive snap connect command works
-
Connecting Snapshot copies on mirrored storage systems
- Snapshot connect and Snapshot restore operations
-
Guidelines for connecting Snapshot copies
- Information required for using the snapdrive snap connect command
- Connecting to a Snapshot copy that contains LUNs
- Connecting to a Snapshot copy of storage entities other than LUNs
- Connecting to Snapshot copies of shared storage entities other than LUNs
-
Splitting a volume clone or LUN clone
- Estimating the storage space to split a volume clone
- Estimating the storage space to split a LUN clone
- Estimating the storage space using a Snapshot copy
- Starting the volume clone or LUN clone split
- Viewing the status of a volume clone or LUN clone split
- Stopping the volume clone or LUN clone split operation
- Viewing the result of a clone split operation using job ID or file specification
-
Deleting a Snapshot copy
-
Disconnecting a Snapshot copy
- Using the Snapshot disconnect operation
-
Guidelines for disconnecting Snapshot copies
- Information required for using the snapdrive snap disconnect command
- Disconnecting Snapshot copy with LUNs and no storage entities
- Disconnecting Snapshot copy with storage entities
- Disconnecting Snapshot copies with shared storage entities
-
-
Data collection utility
-
Troubleshooting
-
Understanding error messages
-
Common error messages
- SnapDrive storage create command fails when multiple SAN paths are present but multipathing is disabled
- Snap restore operation fails when you have nfsv3 and nfsv4 versions enabled in the host and storage system
- Snap disconnect operation fails to delete cloned volume
- SnapDrive for UNIX reports an error if iSCSI is not running
- Discrepancy in the error code message
- Commands appear blocked
- Volume-based snap restore operation fails in slave node
- Snap restore command fails to mount the file system
- Storage connect operation fails to connect to a LUN created on a storage system using the LUN create command
- SnapDrive for UNIX does not show the supported file system types for storage create operation
- Creating a file system directly on a LUN fails
- After rebooting the host, OS and cluster services fail to start
-
Standard exit status values
- Cleaning up the mapped RDM LUNs in the guest operating system and ESX server
- Volume-based SnapRestore check fails
- Snapshot create and delete operation fails
- Unable to create a Snapshot copy
- Unable to restore a Snapshot copy
- Unable to restart the daemon when host cannot communicate to the storage system
- Unable to start the daemon
- snapdrived start command fails
- SnapDrive commands sometimes result in mounting or unmounting file systems and modify system files
- Some commands are delayed when the storage cluster is in failover mode
- Unable to select a storage stack
- snapdrived stop or snapdrived start command hangs
- SnapDrive for UNIX command displays could not check access error
- Mounting a FlexVol volume fails in NFS environment
- SnapDrive for UNIX incorrectly interprets the dollar sign
- SnapDrive for UNIX storage create command fails while discovering some mapped devices
- SnapDrive for UNIX commands fail with customized LD_LIBRARY_PATH
- Storage area network file specification created with Solaris Volume Manager using iSCSI does not mount automatically
- SnapDrive operations fail in multiple subnet configuration
- SnapDrive for UNIX commands fail when environment variables are set using a command shell
- SnapDrive for UNIX does not automatically delete stale devices in UNIX
- Storage disconnect of disk group fails
-
-
Command reference
-
-
Installation and Administration for IBM AIX
-
SnapDrive for UNIX overview
- What SnapDrive for UNIX does
- Features supported in SnapDrive for UNIX
- Operations performed on stand-alone UNIX systems
- Support for Vserver
- vFiler unit support issues
- Considerations for using SnapDrive for UNIX
-
Management of an LVM and raw entities
- How to manage Snapshot copies of LVM, raw devices, and NFS entities
- Security considerations
- Access permissions on a storage system
- Requirements for storage systems
- Stack requirements
- Supported FC, iSCSI, or NFS configurations
- Limitations
- Limitations of LUNs managed by SnapDrive
- Support for NetAppDataMotion for vFiler
-
Support for volume migration
- What configuration checker is
- Limitations for NFS files or directory trees
- Multipathing in SnapDrive for UNIX
- Thin provisioning in SnapDrive for UNIX
- Volume managers on SnapDrive for UNIX
-
Preparing to install SnapDrive for UNIX
-
Hardware and software configuration
-
Preparing your storage system
-
Host preparation for installing SnapDrive for UNIX
-
-
Installing or upgrading SnapDrive for UNIX
-
Understanding the SnapDrive for UNIX daemon
- What the Web service and daemon are
- Checking the status of the daemon
- Starting the SnapDrive for UNIX daemon
- Changing the default daemon password
-
Stopping the daemon
- Restarting the daemon
- Forcing daemon restart
- Secure daemon communication using HTTPS
- Generating self-signed certificates
- Generating a CA-signed certificate
-
Verifying supported configurations
-
Support for storage system rename
-
Using port set in SnapDrive for UNIX
-
Configuring igroups
- Using Selective LUN Map in SnapDrive for UNIX
-
SnapDrive for UNIX configuration
-
Configuring SnapDrive for UNIX
- What the snapdrive.conf file is
- Configuration options and their default values
- What the SnapDrive configuration wizard does
- SnapDrive configuration wizard
- Some configuration commands
- Using the SnapDrive configuration wizard
- Setting values in the snapdrive.conf file
- Checking the version of SnapDrive for UNIX
-
Configuration information for Vserver
-
Audit, recovery, and trace logging in SnapDrive for UNIX
-
What AutoSupport is
-
Support for multipath access in SnapDrive for UNIX
-
Thin provisioning in SnapDrive for UNIX
-
Multiple subnet configuration
- Automatic detection of host entities
-
What SnapDrive wizards are
-
-
Security features in SnapDrive for UNIX
-
Role-based access control in SnapDrive for UNIX
- What role-based access control (RBAC) in SnapDrive for UNIX is
- SnapDrive for UNIX and Operations Manager console interaction
-
Configuration of role-based access control in SnapDrive for UNIX
- SnapDrive commands and capabilities
- Preconfigured roles for ease of user role configuration
- Automatic storage system update on Operations Manager console
- Multiple Operations Manager console servers
- Operations Manager console unavailable
-
RBAC and storage operation examples
-
FlexClone volumes in SnapDrive for UNIX
-
Storage provisioning in SnapDrive for UNIX
-
Storage operations in SnapDrive for UNIX
-
Storage creation with SnapDrive for UNIX
- Methods for creating storage
- Guidelines for the storage create operation
- Information required for the storage create operation
- Storage creation for LVM entities
- Storage creation for a file system that resides on a LUN
- Creating LUNs without host entities
- Creating a file system on a LUN and setting up the LUN automatically
- Creating a file system on a LUN and specifying the LUN
- Creating an LVM entity and setting up the LUN automatically
- Creating an LVM entity and specifying the LUN
-
Command to use to display available storage
-
Increase in storage size using SnapDrive for UNIX
-
The storage connect command
-
The storage disconnect command
- Methods for disconnecting storage
- Guidelines for the snapdrive storage disconnect command
- Tips for using the storage disconnect command
- Information required for using the snapdrive storage disconnect command
- Command syntax for disconnecting LUNs from the host
- Command syntax for disconnecting a file system created on a LUN from the host
- Command syntax for disconnecting LUNs and storage entities from the host
-
The storage delete command
-
-
Creating and using Snapshot copies in SnapDrive for UNIX
-
What Snapshot operations are in SnapDrive for UNIX
-
Snapshot copy operations
-
Snapshot copies information display
- Command to use to display Snapshot copy information
- Guidelines for displaying Snapshot copies
- Information required for using the snapdrive snap show or list commands
- Displaying Snapshot copies residing on a storage system
- Displaying Snapshot copies of a storage system volume
- Displaying a Snapshot copy
- Other ways to get Snapshot copy names
-
Snapshot copy rename
-
Restoring a Snapshot copy
- Command to use to restore Snapshot copies
-
Restoring Snapshot copies on a destination storage system
- Considerations for restoring a Snapshot copy
- Information required for using the snapdrive snap restore command
- Restoring a Snapshot copy
- Restoring a Snapshot copy from a different host
-
Volume-based SnapRestore
- What volume-based SnapRestore is
- Considerations for using volume-based SnapRestore
- Mandatory checks for volume-based SnapRestore
- Checks that can be overridden by the user
- Volume-based SnapRestore command
- Information about LUNs mapped to local or remote hosts
- Host filespec information for a particular volume
- Volume-based SnapRestore for space reservation
-
Connecting to a Snapshot copy
- How the snapdrive snap connect command works
-
Connecting Snapshot copies on mirrored storage systems
- Snapshot connect and Snapshot restore operations
- Guidelines for connecting Snapshot copies
- Information required for using the snapdrive snap connect command
- Connecting to a Snapshot copy that contains LUNs
- Connecting to a Snapshot copy of storage entities other than LUNs
- Connecting to Snapshot copies of shared storage entities other than LUNs
-
Splitting a volume clone or LUN clone
- Estimating the storage space to split a volume clone
- Estimating the storage space to split a LUN clone
- Estimating the storage space using a Snapshot copy
- Starting the volume clone or LUN clone split
- Viewing the status of a volume clone or LUN clone split
- Stopping the volume clone or LUN clone split operation
- Viewing the result of a clone split operation using job ID or file specification
-
Deleting a Snapshot copy
-
Disconnecting a Snapshot copy
- Using the Snapshot disconnect operation
-
Guidelines for disconnecting Snapshot copies
- Information required for using the snapdrive snap disconnect command
- Disconnecting Snapshot copy with LUNs and no storage entities
- Disconnecting Snapshot copy with storage entities
- Disconnecting Snapshot copies with shared storage entities
-
-
Data collection utility
-
Troubleshooting
-
Understanding error messages
-
Common error messages
- SnapDrive storage create command fails when multiple SAN paths are present but multipathing is disabled
- If a volume is deleted on the Vserver without unmounting the volume on the host system, the snapdrive storage show command displays the incorrect actual path
- Snap restore operation fails when you have nfsv3 and nfsv4 versions enabled in the host and storage system
- Snap disconnect operation fails to delete cloned volume
- SnapDrive for UNIX reports an error if iSCSI is not running
- Discrepancy in the error code message
- Commands appear blocked
- Clustering message appears during SnapRestore
-
Standard exit status values
- Volume-based SnapRestore check fails
- Snapshot create and delete operation fails
- Unable to create a Snapshot copy
- Unable to restore a Snapshot copy
- Unable to restart the daemon when host cannot communicate to the storage system
- (AIX) MPIO cfmode support limited
- Unable to start the daemon
- Ghost device handles in AIX cause longer return time on iSCSI commands
- snapdrived start command fails
- SnapDrive commands sometimes result in mounting or unmounting file systems and modify system files
- Unable to select a storage stack
- snapdrived stop or snapdrived start command hangs
- SnapDrive for UNIX command displays could not check access error
- Mounting a FlexVol volume fails in NFS environment
- SnapDrive for UNIX incorrectly interprets the dollar sign
- SnapDrive for UNIX storage create command fails while discovering some mapped devices
- SnapDrive for UNIX commands fail with customized LD_LIBRARY_PATH
- SnapDrive operations fail in multiple subnet configuration
- SnapDrive for UNIX commands fail when environment variables are set using a command shell
- Cannot install SnapDrive for UNIX patches on AIX by default
- SnapDrive for UNIX does not automatically delete stale devices in UNIX
-
-
Command reference
-
- Legal notices