Filter
Top Products
Configuration: Premium Feature—Snapshot Virtual Disks 157
– Use free capacity on the same disk group where the source virtual disk
resides.
– Use free capacity on another disk group.
– Use unconfigured capacity and create a new disk group for the
snapshot repository virtual disk.
– It is recommended placing the snapshot repository virtual disk within
the disk group of the source virtual disk. This ensures that if drives
associated with the disk group are moved to another storage array, all
the virtual disks associated with the snapshot virtual disk remain in
the same group.
• Snapshot Repository Virtual Disk Capacity—The snapshot repository
virtual disk capacity is expressed as a percentage of the source virtual disk
capacity. The maximum percentage allowed is 120 percent.
• Percent Full—When the snapshot repository virtual disk reaches the user-
specified repository full percentage level, the event is logged in the Major
Event Log (MEL). The default snapshot repository full percentage level is
50% of the source virtual disk.
• Snapshot Repository Virtual Disk Full Conditions—Choose whether to
fail writes to the source virtual disk or fail the snapshot virtual disk when
the snapshot repository virtual disk becomes full.
• Host-to-Virtual Disk Mapping—Choose whether to map the snapshot
virtual disk to a host or host group now or to map the snapshot virtual disk
later. The default setting is Map later.
Preparing Host Servers to Create the Snapshot Using the Advanced Path
NOTE: Before using the Snapshot Virtual Disks Premium Feature in a Microsoft
Windows clustered configuration, you must first map the snapshot virtual disk to
the cluster node that owns the source virtual disk. This ensures that the cluster
nodes correctly recognize the snapshot virtual disk.
NOTE: Mapping the snapshot virtual disk to the node that does not own the source
virtual disk before the Snapshot enabling process is completed can result in the
operating system mis-identifying the snapshot virtual disk. This, in turn, can result in
data loss on the source virtual disk or an inaccessible snapshot.
NOTE: For details on mapping the snapshot virtual disk to the secondary node,
refer to the
Dell PowerVault MD3600i and MD3620i Storage Arrays With Microsoft
Windows Server Failover Clusters
on support.dell.com/manuals.
book.book Page 157 Thursday, December 9, 2010 3:20 PM