Limitations of LUNs managed by SnapDrive
-
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...
When working with SnapDrive, you must be aware of the limitations related to LUNs.
-
A LUN managed by SnapDrive cannot serve either as a boot disk or a system disk.
-
The Linux hosts have operating system limits on how many LUNs you can create.
You can run the
snapdrive config check luns
command when you create the LUNs on these hosts. This command enables you to determine how many LUNs you can create. -
SnapDrive does not support the colon (:) in the long forms of the names for LUNs and Snapshot copies.
The colon is allowed between the components of a long Snapshot copy name or between the storage system name and storage system volume name of a LUN. For example,
toaster:/vol/vol1:snap1
is a typical long Snapshot name, whiletoaster:/vol/vol1/lunA
is a typical long LUN name.