Virtual volume details legend
This page is a full legend for the graphical representation of virtual volume details in the IBM® TS7700.
Legend
The following terms are used in the
legend:
- Owning cluster
- The cluster that currently has a volume mounted, or likely mounted it last. Each virtual volume must be owned at all times by one of the configured clusters.
- Primary cache
- The cache used during the last host access of a volume copy. The primary cache can be, but is not always, associated with the owning cluster.
- Primary physical volume
- The physical volume containing the first stacked copy of the virtual
volume within the attached physical library. The primary physical
volume is also the physical volume that is preferred as the source
for a virtual volume when a recall into cache is required. Note: A primary physical volume for each virtual volume can exist on each cluster. However, for each virtual volume there can be only one owning cluster.
- Secondary physical volume
- When duplexing is enabled, each virtual volume is copied to two
physical volumes. The secondary physical volume is the second copy
of the volume. If a recall from the primary physical volume fails,
the secondary physical volume is selected as the source for a virtual
volume's recall into cache.Note: If copy export is utilized, the secondary physical volume can be exported and would therefore not exist in the attached library. In this case, if the primary physical volume fails the secondary physical volume cannot be used as a secondary source of a recall.
Note: The virtual volume details legend
image is divided into virtual, physical, and pending sections. If
the cluster does not possess a physical library, only the virtual
section is visible.
Icon | Description |
---|---|
Data is available in the cloud | |
Data is migrated in the cloud | |
No data exists in the cloud | |
Data is premigrated in the cloud | |
A flash copy is active on the cluster. Note: Volume properties between the
live copy and the flash copy may not have changed.
|
|
The blue star represents the primary partition for tape/cloud partitions. | |
If DS8K offload is implemented and we have object partitions, the green star represents the "primary object partition". | |
Virtual volume not in primary cache. The volume was in the primary cache, but has since been migrated. The current cluster may or may not be the owner. This volume should never be mounted. | |
Virtual volume not in cache on the owning cluster.† | |
Virtual volume in cache. | |
Virtual volume in primary cache.† The current cluster may or may not be the owner. This volume can be mounted. | |
Virtual volume mounted for access. | |
Virtual volume mount in progress. | |
Virtual volume stacked on primary physical volume.‡ | |
Virtual volume stacked on secondary physical volume. | |
Primary physical volume mounted for accessing this virtual volume.‡ | |
Primary physical volume mounted for accessing another virtual volume.‡ | |
Secondary physical volume mounted for accessing this virtual volume. | |
Secondary physical volume mounted for accessing another virtual volume. | |
Pending action: virtual volume in incoming copy queue (icon is above Virtual Action areas). | |
Pending action: virtual volume deferred in incoming copy queue. | |
Pending action: virtual volume in recall queue. | |
Pending action: virtual volume migrating (icon is between Virtual and Physical Action areas). | |
†When applied to the cache icon,
a green star signifies the owning cluster. ‡When applied to the physical volume icon, a green star signifies a primary physical volume, or the first physical volume written to when a virtual volume is migrated to physical tape. |