Dell MD3620I, MD3600I Virtual Disk Copy Restrictions, Creating a Virtual Disk Copy, 172

Virtual Disk Copy Restrictions

Before you perform any virtual disk copy tasks, understand and adhere to the restrictions listed in this section. The restrictions apply to the source virtual disk, the target virtual disk, and the storage array.

•While a virtual disk copy has a status of In Progress, Pending, or Failed, the source virtual disk is available for read I/O activity only. After the virtual disk copy is complete, read and write I/O activity to the source virtual disk are permitted.

•A virtual disk can be selected as a target virtual disk for only one virtual disk copy at a time.

•A virtual disk copy for any virtual disk cannot be mounted on the same host as the source virtual disk.

•Windows does not allow a drive letter to be assigned to a virtual disk copy.

•A virtual disk with a Failed status cannot be used as a source virtual disk or target virtual disk.

•A virtual disk with a Degraded status cannot be used as a target virtual disk.

•A virtual disk participating in a modification operation cannot be selected as a source virtual disk or target virtual disk. Modification operations include the following:

–Capacity expansion

–RAID-level migration

–Segment sizing

–Virtual disk expansion

–Defragmenting a virtual disk

NOTE: The following host preparation sections also apply when using the virtual disk copy feature through the CLI interface.

Creating a Virtual Disk Copy

CAUTION: Possible loss of data—Source virtual disks that are participating in a virtual disk copy are available for read I/O activity only while a virtual disk copy has a status of In Progress or Pending. Write requests are allowed after the virtual disk copy has completed. If the source virtual disk has been formatted with a

172

Configuration: Premium Feature—Virtual Disk Copy