Table of ContentsView in Frames

Managing LUNs not created in SnapDrive

You can use SnapDrive for Windows to manage LUNs not created by SnapDrive by preparing 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.
  • The ostype of the LUN must match the partition style and the type of OS accessing it, as follows:
    Windows OS and partition style ostype
    Windows Server 2008 (MBR or GPT partitioned) windows_2008
    Windows Server 2008 Hyper-V (MBR or GPT partitioned) hyper_v
    Windows Server 2012 (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. You can use OnCommand System Manager to check the ostype of the LUN. For more information about ostype, see the Data ONTAP SAN Administration Guide for 7-Mode.

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

  1. If you have a clustered Windows configuration, perform the following steps:
    1. In SnapDrive, create a shared disk on the storage system to temporarily designate as the quorum disk.
    2. Right-click the resource and select Properties > Dependencies to record all dependencies for each resource in this cluster group, using the Windows cluster management console.

    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 enabled or that there is enough space available for space reservation to be enabled.
  2. Shut down the stand-alone Windows host, or all nodes in a cluster.

    Shutting down your Windows hosts ensures that all data has been flushed and that Snapshot copies are consistent.

  3. Using OnCommand System Manager or the storage system console, complete the following steps:
    1. Unmap the LUN from the initiator group.
    2. Make a Snapshot copy of the volume on which the LUNs reside.
  4. Restart the stand-alone Windows host, or all nodes in a cluster.
  5. If you have a clustered Windows configuration, delete the shared disk resource using the Windows cluster management console.
  6. Connect to the LUN using SnapDrive.
  7. If you are working in a Windows cluster, perform the following substeps:
    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.
  8. Using SnapDrive, make a Snapshot copy of the newly connected LUN.