Administrator Guide

The number of volumes and virtual snapshots for the pool owned by the controller appears above the top horizontal bar for both virtual
and linear storage.
Hover the cursor anywhere in a storage block to display the Storage Information panel. The Storage Information panel only contains
information for the type of storage that you are using.
Table 6. Storage information
Storage type Information displayed for the storage type
Virtual pool
• Owner, storage type, total size, allocated size, snapshot size, available size, allocation rate,
and deallocation rate
• For each tier: Pool percentage, number of disks, total size, allocated size, unallocated size,
number of reclaimed pages, and health
• If the pool health is not OK, an explanation and recommendations for resolving problems
with unhealthy components is available. If the overall storage health is not OK, the health
reason, recommended action, and unhealthy subcomponents are shown to help you
resolve problems.
Linear pool
• Owner, storage type, total size, allocated size, and available size
• If the pool health is not OK, an explanation and recommendations for resolving problems
with unhealthy components is available. If the overall storage health is not OK, the health
reason, recommended action, and unhealthy subcomponents are shown to help you
resolve problems.
System health information
The health icon between the storage blocks indicates the health of the system. Hover the cursor over this icon to display the System
Health panel, which shows more information about the health state. If the system health is not OK, the System Health panel also shows
information about resolving problems with unhealthy components.
Spares information
The Spares block between the storage blocks and below the event icon shows the number of disks that are designated as global spares to
automatically replace a failed disk in the system. Hover the cursor over the Spares block to see the disk types of the available global spares
in the Global Spares Information panel.
Resolving a pool conflict caused by inserting a foreign disk
group
If you insert a virtual disk group from an old system into a new system, the new system attempts to create a virtual pool for that disk
group. If that system already has a virtual pool with the same name, the pool for the inserted disk group will be offline. For example, if the
new system has a pool A and you insert a disk group that came from pool A on the old system, the imported pool A from old system will be
offline.
This type of operation is not common, and you should consider your conflict resolution options carefully. To resolve this conflict, do either
of the following:
• If the pool conflict was expected—for example, you want to access data on the disk group from pool A of the old system:
1. Unmount and unmap the LUNs from any host accessing volumes on the new system.
2. Stop I/O from hosts accessing any volumes on the new system and power down the new system.
3. Physically remove all disks for the original pool A of the new system.
4. Insert the disks from pool A of the old system.
5. Restore power to the new system. The data on the disk group from pool A of the old system is now accessible.
6. Copy that data to pool B on the new system.
7. After you have copied the data to the new system, remove the disks from old system and reinsert the disks from the new system.
8. Remap and remount the LUNs to any host that requires access to volumes on pool A of the new system.
Working in the Home topic
37