Configuration: PremiumFeature—Virtual Disk Copy 173
journaling file system, any attempt to issue a read request to the source virtual
disk might be rejected by the storage array, and an error message might appear.
The journaling file system driver issues a write request before it attempts to issue
the read request. The storage array rejects the write request, and the read request
might not be issued due to the rejected write request. This condition might result
in an error message appearing, which indicates that the source virtual disk is
write protected. To prevent this issue from occurring, do not attempt to access a
source virtual disk that is participating in a virtual disk copy while the virtual disk
copy has a status of In Progress. Also, make sure that the Read-Only attribute for
the target virtual disk is disabled after the virtual disk copy has completed to
prevent error messages from appearing.
The Virtual Disk Copy premium feature includes these items:
•The
Create Copy Wizard
, which assists in creating a virtual disk copy
•The
Copy Manager
, which monitors virtual disk copies after they have
been created
Before you Begin
A virtual disk copy fails all snapshot virtual disks that are associated with the
target virtual disk, if any exist. If you select a source virtual disk of a snapshot
virtual disk, you must disable all of the snapshot virtual disks that are
associated with the source virtual disk before you can select it as a target
virtual disk. Otherwise, the source virtual disk cannot be used as a target
virtual disk.
A virtual disk copy overwrites data on the target virtual disk and automatically
makes the target virtual disk read-only to hosts
If eight virtual disk copies with a status of In Progress exist, any subsequent
virtual disk copy has a status of Pending, which stays until one of the eight
virtual disk copies completes.
Virtual Disk Copy and Modification Operations
If a modification operation is running on a source virtual disk or a target
virtual disk, and the virtual disk copy has a status of In Progress, Pending, or
Failed, the virtual disk copy does not take place. If a modification operation is
running on a source virtual disk or a target virtual disk after a virtual disk copy
has been created, the modification operation must complete before the
virtual disk copy can start. If a virtual disk copy has a status of In Progress, any
modification operation does not take place.
book.book Page 173 Thursday, December 9, 2010 3:20 PM