The
Secure Physical Disks
option is displayed in the
Disk Pool
menu. The
Secure Physical Disks
option is active if these conditions are
true:
•
The selected storage array is not security enabled but is comprised entirely of security capable physical disks.
•
The storage array contains no snapshot copy base virtual disks or snapshot repository virtual disks.
•
The disk pool is in Optimal status.
•
A security key is set up for the storage array.
The
Secure Physical Disks
option is inactive if the preceding conditions are not true. The
Secure Physical Disks
option is inactive with a
check mark to the left if the disk pool is already security enabled.
The
Create a secure disk
pool option is displayed in the
Create Disk Pool - Disk Pool Name and Physical Disk Selection
dialog. The
Create a secure disk pool
option is active only when the following conditions are met:
•
The Physical Disk Security feature is activated.
•
A security key is installed in the storage array.
•
At least one security capable physical disk is installed in the storage array.
•
All the physical disks that you selected on the
Hardware
tab are security capable physical disks.
Changing capacity on existing thin virtual disks
If the amount of space used by the host for read/write operations (sometimes called consumed capacity) exceeds the amount of physical
capacity allocated on a standard virtual disk, the storage array cannot accommodate additional write requests until the physical capacity is
increased. However, on a thin virtual disk, MD Storage Manager can automatically expand physical capacity of a thin virtual disk. You can
also do it manually using
Storage
>
Virtual Disk
>
Increase Repository Capacity.
If you select the automatic expansion option, you can
also set a maximum expansion capacity. The maximum expansion capacity enables you to limit the automatic growth of a virtual disk to an
amount less than the defined virtual capacity.
NOTE:
Because less than full capacity is allocated when you create a thin virtual disk, insufficient free capacity may exist when
certain operations are performed, such as snapshot images and snapshot virtual disks. If this occurs, an alert threshold warning
is displayed.
Creating thin virtual disk from disk pool
NOTE:
You can create thin virtual disks only from disk pools, not from disk groups.
1
In the AMW, select the
Storage & Copy Services
tab.
2
Select a
Free Capacity
node in a disk pool.
The thin virtual disks are listed under the
Disk Pools
node.
3
Select
Storage
>
Virtual Disk
>
Create
>
Virtual Disk.
The
Create Virtual Disk
window is displayed.
4
Select
Create thin virtual disk
.
5
Use the
New virtual capacity
box to indicate the virtual capacity of the new virtual disk and
Units
to indicate the specific capacity
units to use—MB, GB, or TB.
The minimum virtual capacity is 32 MB.
6
In the
Virtual disk name
box, enter a name for the virtual disk.
7
To map hosts to virtual disks, select
Map later
.
The virtual disk is not assigned a LUN and is not accessible by any hosts until you go to the
Host Mappings
tab and assign a specific
host and LUN to this virtual disk.
8
To use flash SSD cache, select
Use flash SSD cache
.
Flash SSD cache provides read-only caching of user-selected virtual disks on Solid-State Disks (SSDs) to further improve the read
performance of those virtual disks beyond conventional hard drives. This process of copying data transparently off hard drives and on
to high-performance SSDs improves application I/O performance and response times.
102
Disk pools and disk pool virtual disks
