Administrator Guide

• Over Threshold — Physical capacity of a thin virtual disk is at or beyond the specified Warning Threshold percentage. The storage
array status is shown as Needs Attention.
• Failed — Virtual disk failed, and is no longer available for read or write operations. The storage array status is shown as Needs
Attention.
Comparison—Types of virtual disks and copy services
The availability of copy services depends on the type of virtual disk that you are working with.
Table 9. Copy services features supported on each type of virtual disk
Copy Services Feature Standard Virtual Disk in a Disk
Group
Standard Virtual Disk in a Disk
Pool
Thin Virtual Disk
Snapshot image Supported Supported Supported
Snapshot virtual disk Supported Supported Supported
Rollback of snapshot Supported Supported Supported
Delete virtual disk with
snapshot images or snapshot
virtual disks
Supported Supported Supported
Consistency group
membership
Supported Supported Supported
Remote Replication (Legacy) Supported Not supported Not supported
Remote Replication Supported Supported Not supported
The source of a virtual disk copy can be either a standard virtual disk in a disk group, a standard virtual disk in a disk pool, or a thin virtual
disk. The target of a virtual disk copy can be only a standard virtual disk in a disk group or a standard virtual disk in a disk pool, not a thin
virtual disk.
Table 10. Types of virtual disk
Virtual Disk Copy Source Virtual Disk Copy Target Availability
Standard virtual disk Standard virtual disk Supported
Thin virtual disk Standard virtual disk Supported
Standard virtual disk Thin virtual disk Not supported
Thin virtual disk Thin virtual disk Not supported
Rollback on thin virtual disks
Rollback operations are fully supported on thin virtual disks. A rollback operation restores the logical content of a thin virtual disk to match
the selected snapshot image. There is no change to the consumed capacity of the thin virtual disk as a result of a rollback operation.
Initializing a thin virtual disk
CAUTION:
Possible loss of data – Initializing a thin virtual disk erases all data from the virtual disk. If you have
questions, contact your Technical Support representative before performing this procedure.
When a thin virtual disk is created, it is automatically initialized. However, the MD Storage Manger Recovery Guru may advise that you
manually initialize a thin virtual disk to recover from certain failure conditions. If you choose to reinitialize a thin virtual disk, you have
several options:
• Keep the same physical capacity — If you keep the same physical capacity, the virtual disk can keep its current repository virtual disk,
which saves initialization time.
• Change the physical capacity — If you change the physical capacity, a new repository virtual disk is created and you can optionally
change the repository expansion policy and warning threshold.
• Move the repository to a different disk pool.
64
Disk groups, standard virtual disks, and thin virtual disks