Administrator Guide

Initializing a thin virtual disk erases all data from the virtual disk. However, host mappings, virtual capacity, repository expansion policy and
security settings are preserved. Initialization also clears the block indices, which causes unwritten blocks to be read as if they are zero-
filled. After initialization, the thin virtual disk appears to be completely empty.
The following types of virtual disks cannot be initialized:
• Base virtual disk of a Snapshot virtual disk
• Primary virtual disk in a Remote Replication relationship
• Secondary virtual disk in a Remote Replication relationship
• Source virtual disk in a Virtual Disk Copy
• Target virtual disk in a Virtual Disk Copy
• Thin virtual disk that already has an initialization in progress
• Thin virtual disk that is not in the Optimal state
Initializing thin virtual disk with same physical capacity
CAUTION: Initializing a thin virtual disk erases all data from the virtual disk.
• You can create thin virtual disks only from disk pools, not from disk groups.
• By initializing a thin virtual disk with the same physical capacity, the original repository is maintained but the contents of the thin virtual
disk are deleted.
1. In the AMW, select the Storage & Copy Services tab.
2. Select the thin virtual disk that you want to initialize.
The thin virtual disks are listed under the Disk Pools node.
3. Select Storage > Virtual Disk > Advanced > Initialize.
The Initialize Thin Virtual Disk window is displayed.
4. Select Keep existing repository, and click Finish.
The Confirm Initialization of Thin Virtual Disk window is displayed.
5. Read the warning and confirm if you want to initialize the thin virtual disk.
6. Type yes, and click OK.
The thin virtual disk initializes.
Initializing thin virtual disk with different physical capacity
CAUTION: Initializing a thin virtual disk erases all data from the virtual disk.
• You can create thin virtual disks only from disk pools, not from disk groups.
• By initializing a thin virtual disk with the same physical capacity, the original repository is maintained but the contents of the thin virtual
disk are deleted.
1. In the AMW, select the Storage & Copy Services tab.
2. Select the thin virtual disk that you want to initialize.
The thin virtual disks are listed under the Disk Pools node.
3. Select Storage > Virtual Disk > Advanced > Initialize.
The Initialize Thin Virtual Disk window is displayed.
4. Select Use a different repository.
5. Based on whether you want to keep the current repository for future use, select or clear Delete existing repository, and click Next.
6. Select one of the following:
• Yes—If there more than one disk pool on your storage array
• No—If there is only one disk pool on your storage array
The Select Disk Pool window is displayed.
7. Select Keep existing disk pool, and click Next.
The Select Repository window is displayed.
8. Use the Preferred capacity box to indicate the initial physical capacity of the virtual disk and the Units list to indicate the specific
capacity units to use—MB, GB, or TB.
NOTE:
Do not allocate all the capacity to standard virtual disks—ensure that you keep storage capacity for copy
services (snapshot images, snapshot virtual disks, virtual disk copies, and remote replications).
NOTE: Regardless of the capacity specified, capacity in a disk pool is allocated in 4 GB increments. Any capacity that
is not a multiple of 4 GB is allocated but not usable. To make sure that the entire capacity is usable, specify the
Disk groups, standard virtual disks, and thin virtual disks 65