To avoid problems creating LUNs when using SnapDrive, you must keep some rules in mind.
- Create LUN names using US-ASCII characters only, even when you are using non-ASCII operating systems.
- If you are adding the LUN to a Windows Server 2003 or 2008 cluster, make sure to create the LUN on the node that owns the cluster group in which you are creating a new physical disk resource.
Note: - Shared disks on Windows Server 2003 cluster nodes that do not own the disks often display as unknown and unreadable, and as offline on Windows 2008, in MMC Disk Management utility; however, the disks will continue to function normally on all nodes in the cluster.
- Use the LUN path instead of the UNC path to create a LUN. When you use the UNC path, disk creation fails with the error: A device attached to the system is not functioning.
- Use Disk Management in MMC to assign a drive letter and format the LUN manually. When you try to create a LUN using the disk create command, it might fail with the error: VDS disk object for the LUN s/n 'xyz' has not been found.
- To ensure that Snapshot copies can be made, follow these guidelines:
- Do not attempt to create a LUN on a storage system volume that holds anything other than LUNs.
- Conversely, do not put anything other than LUNs on a storage system volume that contains LUNs.
- All LUNs in the same storage system volume should be created using SnapDrive or, if they were created outside of SnapDrive, prepared for management in SnapDrive.
