Managing LUNs not created in SnapDrive

You can use SnapDrive for Windows to manage LUNs not created by SnapDrive by completing these steps to prepare the LUNs for SnapDrive management.

Before you begin

The names of LUNs, qtrees, igroups, volumes, and storage systems must use US-ASCII characters only.
The LUN should have a single partition on an NTFS file system.

If the ostype of the LUN is mismatched to the partition style and the type of OS accessing it, there will be significant performance degradation. Refer to the following table to see which ostype your LUNs should have.

Windows OS and partition style	ostype
Windows Server 2003 (MBR partitioned)	`windows`
Windows Server 2003 (GPT partitioned)	`windows_gpt`
Windows Server 2008 (MBR or GPT partitioned)	`windows_2008`
Windows Server 2008 Hyper-V (MBR or GPT partitioned)	`hyper_v`

If the LUN was created with ostype set to a different value than you need, you can create a new LUN using SnapDrive, copy the data to it, and delete the original LUN. For more information about ostype, see the Data ONTAP Block Access Management Guide for iSCSI and FC.

Note: In earlier versions of SnapDrive, LUNs were required to have the .lun extension to be managed by SnapDrive; however, .lun extensions are no longer required as of SnapDrive 4.2.

Steps

If you have a clustered Windows configuration, complete the procedure in this step. Otherwise, go to the next step.
1. In SnapDrive, create a shared disk on the storage system to temporarily designate as the quorum disk.
2. For each resource in this cluster group, record all dependencies by using the Windows cluster management console.
  Right-click the resource and select Properties > Dependencies.
3. Designate the newly created disk as the quorum on the owning node of your Windows cluster using the Windows cluster management console. For information about how to set a disk as a quorum, see your Windows documentation.
4. Check that space reservation is on or that there is enough space available for space reservation to be turned on.
Shut down the stand-alone Windows host, or all nodes in a cluster.
Note: Shutting down your Windows hosts ensures that all data has been flushed and that Snapshot copies are consistent.
Using the FilerView or the storage system console, complete the following steps:
1. Unmap the LUN from the initiator group.
2. Take a Snapshot copy of the volume on which the LUNs reside.
Restart the stand-alone Windows host, or all nodes in a cluster.
If you have a clustered Windows configuration, Windows sees the unmapped LUN as a surprise disk removal, and the disk resource is reported as "failed." Before attempting to reconnect the LUN, you need to delete the shared disk resource using the Windows cluster management console.
Connect to the LUN using SnapDrive.
If you are working in a Windows cluster, complete the procedure in this step. Otherwise, go to the next step.
1. Designate the newly connected LUN as the quorum using the Windows cluster management console on the owning node of your cluster.
2. Re-create any dependencies you recorded in Step 1.
3. Delete the temporary disk you created in Step 1.
Using SnapDrive, take a Snapshot copy of the newly connected LUN.