Virtual volume details
Use this page to obtain detailed information about the state of a virtual volume or a FlashCopy of a virtual volume in the IBM® TS7700 Grid.
To obtain details about a virtual volume or FlashCopy, enter the VOLSER belonging to the virtual volume in the VOLSER of Virtual Volume field, then click the Get Details button. The VOLSER must be six alphanumeric characters.
You can view details and status of a virtual volume in a cluster by using the Virtual
volume summary image or the Virtual volume details table. You can
also use the Cluster-specific virtual volume properties table to view
information about virtual volume properties specific to a cluster.
Note: If the cluster does not
possess a physical library, physical resources are not shown in the Virtual volume
summary image, Virtual volume details table, or the
Cluster-specific virtual volume properties table.
If a
FlashCopy exists for the virtual volume, the FlashCopy lightning icon is shown on the
Virtual volume summary image and the FlashCopy field is
displayed on the Virtual volume details table. For more information, see the
FlashCopy entry on Table 1.- Virtual volume summary
- The Virtual volume summary figure displays the details and status of
virtual volumes in a grid, arranged by cluster. For a description of the icons that are shown on
this summary, refer to the topic Virtual volume details legend in the
Related information section. Refer to this topic to understand the difference between cache
and primary cache.
Each cluster that is shown in the Virtual volume summary image is divided into virtual and physical sections. The physical section is only shown when a cluster possesses a physical library. In the Virtual volume summary image, the highlighted cluster is the cluster that currently owns the queried virtual volume. Volumes that are shown in this image are represented by icons that display the status of the volume.
- Virtual volume details
- The Virtual volume details table displays details and status of a virtual volume in a cluster. These virtual volume properties are consistent across the grid.
-
Table 1. Virtual volume details and status Volume detail Description Volser The VOLSER of the virtual volume. This value is a six-character number that uniquely represents the virtual volume in the virtual library. Media Type The media type of the virtual volume. Possible values are: - Cartridge System Tape
- Enhanced Capacity Cartridge System Tape
Maximum Volume Capacity (Channel or Device) The maximum size (MiB) of the virtual volume. This capacity is set upon insert by the Data Class of the volume. Note: If an override is configured for the data class's maximum size, it is only applied when a volume is mounted and a load-point write (scratch or fast ready mount) occurs. During the volume close operation, the new override value is bound to the volume and cannot change until the volume is reused. Any further changes to a data class override are not inherited by a volume until it is written again during a fast ready mount and then closed.Note: When the host mounts a scratch volume and demounts it without completing any writes, the system might report that the virtual volume's current size is larger than its maximum size. This result can be disregarded.Current Volume Size (Channel or Device) Size of the data (MiB) for this unit type (channel or device). Note: Refer to the topic Data storage values in the Related Information section for additional information concerning the use of binary prefixes.Channel Size The number of channel bytes written to the volume. Also called Nominal Size. If the selected cluster is a deduplication cluster, this value is the same as the Current Volume Size.
If the selected cluster is not a deduplication cluster, this value is not applicable and shown as " —".
Current Owner The name of the cluster that currently owns the latest version of the virtual volume. Currently Mounted Whether the virtual volume is currently mounted in a virtual drive. If this value is Yes these qualifiers are also shown: - vNode
- The name of the vNode that the virtual volume is mounted on.
- Virtual Drive
- The ID of the virtual drive the virtual volume is mounted on.
Cache Copy Used for Mount The name of the cluster that owns the cache chosen for I/O operations for mount. This selection is based on consistency policy, volume validity, residency, performance, and cluster mode. Mount State The mount state of the logical volume. Possible values are: - Mounted
- The volume is mounted.
- Mount Pending
- A mount request was received and is in progress.
- Recall Queued/Requested
- A mount request was received and a recall request was queued.
- Recalling
- A mount request was received and the virtual volume is being staged into tape volume cache from physical tape.
Cache Management Preference Group The preference level for the storage group; it determines how soon volumes are removed from cache following their copy to tape. This information is only displayed if the owner cluster is a TS7700T and the volume is assigned to a cache partition that is greater than 0. Possible values are: - 0
- Volumes in this group have preference to be removed from cache over other volumes.
- 1
- Volumes in this group have preference to be retained in cache over other volumes. A "least recently used" algorithm is used to select volumes for removal from cache if there are no volumes to remove in preference group 0.
- Unknown
- The preference group cannot be determined.
Last Accessed by a Host The most recent date and time a host accessed a live copy of the virtual volume. Time that is recorded reflects the time zone in which the user's browser is located. Last Modified The date and time the virtual volume was last modified by a host mount or demount. Time that is recorded reflects the time zone in which the user's browser is located. Category The number of the Fast Ready category to which the virtual volume belongs. A Fast Ready category groups virtual volumes for quick, non-specific use. Storage Group The name of the Storage Group that defines the primary pool for the pre-migration of the virtual volume. Management Class The name of the Management Class applied to the volume. This policy defines the copy process for volume redundancy. Storage Class The name of the Storage Class applied to the volume. This policy classifies virtual volumes to automate storage management. Data Class The name of the Data Class applied to the volume. This policy classifies virtual volumes to automate storage management. Volume Data State The state of the data on the virtual volume. Possible values are: - New
- The virtual volume is in the insert category or a non-fast-ready category and data has never been written to it.
- Active
- The virtual volume is currently located within a private category and contains data.
- Scratched
- The virtual volume is currently located within a fast ready (scratch) category and its data is not scheduled to be automatically deleted.
- Pending Deletion
- The volume is currently located within a fast ready (scratch) category and its contents are a
candidate for automatic deletion when the earliest deletion time has passed. Automatic deletion then
occurs sometime thereafter. Note: The volume can be accessed for mount or category change before the automatic deletion and therefore the deletion can be incomplete.
- Pending Deletion with Hold
- The volume is currently located within a fast ready (scratch) category configured with hold and the earliest deletion time has not yet passed. The volume is not accessible by any host operation until the volume has left the hold state. Once the earliest deletion time has passed, the volume then becomes a candidate for deletion and move to the Pending Deletion state. While in this state, the volume is accessible by all legal host operations.
- Deleted
- The volume is either currently within a fast ready category or has previously been in a fast ready category where it became a candidate for automatic deletion and was deleted. Any mount operation to this volume is treated as a fast ready (scratch) mount since no data is present.
FlashCopy Details of any existing flash copies. Note: This field is only shown if the grid contains a disk-only, non-deduplication cluster.Possible values include:- Not Active
- No FlashCopy is active. No FlashCopy was enabled at the host by an LI REQ operation.
- Active
- A FlashCopy that affects this volume was enabled at the host by an LI REQ operation. Volume properties have not changed since FlashCopy time zero.
- Created
- A FlashCopy that affects this volume was enabled at the host by an LI REQ operation. Volume properties between the live copy and the FlashCopy have changed.
- Click this value to open the Flash Copy Details page.
Earliest Deletion On The date and time when the virtual volume is deleted. Time that is recorded reflects the time zone in which your browser is located. This value displays as "—" if no expiration date is set.
Logical WORM Whether the virtual volume is formatted as a write-once, read many (WORM) volumes. Possible values are Yes and No.
Compression Method The compression method applied to the volume. Volume Format ID Volume format ID that belongs to the volume. Possible values include: - -2 - Data has not been written yet
- 5 - Logical Volume old format
- 6 - Logical Volume new format
3490 Counters Handling 3490 Counters Handling value that belongs to the volume Note: A single dash (—) is used to indicate an empty value in fields where a value is not present or applicable. - Cluster-specific virtual volume properties
- The Cluster-specific virtual volume properties table displays information about requesting virtual volumes on each cluster. These are properties that are specific to a cluster.
-
Table 2. Cluster-specific virtual volume properties Property Description Cluster The cluster location of the virtual volume copy. Each cluster location occurs as a separate column header. In Cache Whether the virtual volume is in cache for this cluster. Device Bytes Stored The number of bytes used (MiB) by each cluster to store the volume. Actual bytes can vary between clusters, based on settings and configuration. Values are defined as either Device or Channel bytes. Primary Physical Volume The physical volume that contains the specified virtual volume. Click the VOLSER hyperlink to open the Physical Stacked Volume Details page for this physical volume. A value of None means that no primary physical copy is to be made. This column is only visible if a physical library is present in the grid. If there is at least one physical library in the grid, the value in this column is shown as "—" for those clusters that are not attached to a physical library. Secondary Physical Volume Secondary physical volume that contains the specified virtual volume. Click the VOLSER hyperlink to open the Physical Stacked Volume Details page for this physical volume. A value of None means that no secondary physical copy is to be made. This column is only visible if a physical library is present in the grid. If there is at least one physical library in the grid, the value in this column is shown as "—" for those clusters that are not attached to a physical library. Copy Activity Status information about the copy activity of the virtual volume copy. Possible values are: - Complete
- This cluster location completed a consistent copy of the volume.
- In Progress
- A copy is required and currently in progress.
- Required
- A copy is required at this location but has not started or completed.
- Not Required
- A copy is not required at this location.
- Reconcile
- Pending updates exist against this location's volume. The copy activity updates after the pending updates get resolved.
- Time Delayed Until [time]
- A copy is delayed as a result of Time Delayed Copy mode. The value for
[time]is the next earliest date and time that the volume is eligible for copies.
Queue Type The type of queue as reported by the cluster. Possible values are: - Rewind Unload (RUN)
- The copy occurs before the rewind-unload operation completes at the host.
- Deferred
- The copy occurs some time after the rewind-unload operation completes at the host.
- Sync Deferred
- The copy was set to be synchronized, according to the synchronized mode copy settings, but the synchronized cluster could not be accessed. The copy is in the deferred state. For more information about synchronous mode copy settings and considerations, see Synchronous mode copy in the Related information section.
- Immediate Deferred
- A RUN copy that was moved to the deferred state due to copy timeouts or TS7700 Grid states.
- Time Delayed
- The copy occurs sometime after the delay period has been exceeded.
Copy Mode The copy behavior of the virtual volume copy. Possible values are: - Rewind Unload (RUN)
- The copy occurs before the rewind-unload operation completes at the host.
- Deferred
- The copy occurs some time after the rewind-unload operation at the host.
- No Copy
- No copy is made.
- Sync
- The copy occurs upon any synchronization operation. For more information about synchronous mode copy settings and considerations, see the topic Synchronous mode copy in the Related information section.
- Time Delayed
- The copy occurs sometime after the delay period has been exceeded.
- Exist
- A consistent copy exists at this location although No Copy is intended. A consistent copy existed at this location at the time the virtual volume was mounted. Once the volume is modified, the Copy Mode of this location changes to No Copy.
Deleted The date and time when the virtual volume on the cluster was deleted. Time that is recorded reflects the time zone in which the user's browser is located. If the volume has not been deleted, this value displays as "—". Removal Residency The automatic removal residency state of the virtual volume. This field is displayed only when the grid contains a disk-only, non-deduplication cluster. In a TS7700 Tape Attach configuration, this field is displayed only when the volume is in the disk partition. Possible values are: - —
- Removal Residency does not apply to the cluster. This value is displayed
if:
- The cluster attaches to a physical tape library.
- Inconsistent data exists on the volume.
- Removed
- The virtual volume has been removed from the cluster.
- No Removal Attempted
- The virtual volume is a candidate for removal, but the removal has not yet occurred.
- Retained
- An attempt to remove the virtual volume occurred, but the operation failed. The copy on this cluster cannot be removed based on the configured copy policy and the total number of configured clusters. Removal of this copy lowers the total number of consistent copies within the grid to a value below the required threshold. If a removal is expected at this location, verify that the copy policy is configured and that copies are being replicated to other peer clusters. This copy can be removed only after enough replicas exist on other peer clusters.
- Deferred
- An attempt to remove the virtual volume occurred, but the operation failed. This state can result from a cluster outage or any state within the grid that disables or prevents replication. The copy on this cluster cannot be removed based on the configured copy policy and the total number of available clusters capable of replication. Removal of this copy lowers the total number of consistent copies within the grid to a value below the required threshold. This copy can be removed only after enough replicas exist on other available peer clusters. A subsequent attempt to remove this volume occurs when no outage exists and replication is allowed to continue.
- Pinned
- The virtual volume is pinned by the virtual volume storage class. The copy on this cluster cannot be removed until it is unpinned. When this value is present, the Removal Time value is Never.
- Held
- The virtual volume is held in cache on the cluster at least until the Removal Time has passed. When the removal time has passed, the virtual volume copy is a candidate for removal. The Removal Residency value becomes No Removal Attempted if the volume is not accessed before the Removal Time passes. The copy on this cluster is moved to the Resident state if it is not accessed before the Removal Time passes. If the copy on this cluster is accessed after the Removal Time has passed, it is moved back to the Held state.
Removal Time This field is displayed only if the grid contains a disk-only, non-deduplication cluster. Values displayed in this field depend on values displayed in the Removal Residency field. Possible values include: - —
- Removal Time does not apply to the cluster. This value is displayed if the cluster attaches to a physical tape library.
- Removed
- The date and time the virtual volume was removed from the cluster.
- Held
- The date and time the virtual volume becomes a candidate for removal.
- Pinned
- The virtual volume is never removed from the cluster.
- No Removal Attempted, Retained, or Deferred
- Removal Time is not applicable.
Volume Copy Retention Group The name of the group that defines the preferred auto removal policy applicable to the virtual volume. This field is displayed only for a TS7700 Cluster or for partition 0 (CP0) on a TS7700 Tape Attach Cluster, and only when the grid contains a disk-only, non-deduplication cluster. The Volume Copy Retention Group provides more options to remove data from a cluster as the active data reaches full capacity. Volumes become candidates for removal if an appropriate number of copies exist on peer clusters AND the volume copy retention time has elapsed.
The Retention Time parameter describes the number of hours a volume remains in cache before becoming a candidate for removal. Retention time is measured beginning at the volume's creation time -- when a write operation was performed from the beginning of a tape -- or at the time the volume was most recently accessed. Volumes in each group are removed in order based on their least recently used access times.
If the virtual volume is in a fast ready category and resides on a disk-only cluster, removal settings no longer apply to the volume and the volume is a candidate for removal. In this instance, the value that is displayed for the Volume Copy Retention Group is accompanied by a warning icon. Possible values are:- —
- Volume Copy Retention Group does not apply to the cluster. This value is displayed if the cluster attaches to a physical tape library.
- Prefer Remove
- Removal candidates in this group are removed prior to removal candidates in the Prefer Keep group.
- Prefer Keep
- Removal candidates in this group are removed after removal candidates in the Prefer Remove group are removed.
- Pinned
- Copies of volumes in this group are never removed from the accessing cluster. The volume copy
retention time does not apply to volumes in this group. Volumes in this group that are subsequently
moved to scratch become priority candidates for removal.CAUTION:Care must be taken when assigning volumes to this group to avoid cache overruns.
Retention Time The length of time, in hours, that must elapse before the virtual volume named in Volume Copy Retention Group can be removed. Depending on the Volume Copy Retention Reference setting, this time period can be measured from the time when the virtual volume was created or when it was most recently accessed. Volume Copy Retention Reference The basis for calculating the time period defined in Retention Time. Possible values are: - Volume Creation
- Calculate retention time starting with the time when the virtual volume was created. This refers to the time a write operation was performed from the beginning of a tape -- either a scratch mount or a private mount where writing began at record 0.
- Volume Last Accessed
- Calculate retention time starting with the time when the virtual volume was most recently accessed.
TVC Preference The group containing virtual volumes that have preference for premigration. This field is displayed only for a TS7700 Cluster or for partitions 1 through 7 (CP1 through CP7) in a TS7700 Tape Attach cluster. Possible values are: - PG0
- Volumes in this group have preference to be premigrated over other volumes.
- PG1
- Volumes in this group have preference to be premigrated over other volumes. A "least recently used" algorithm is used to select volumes for premigration if there are no volumes to premigrate in preference group 0.
Time-Delayed Premigration Delay The length of time, in hours, that must elapse before a delayed premigration operation can begin for the virtual volumes designated by the TVC Preference parameter. Depending on the Time-Delayed Premigration Reference setting, this time period can be measured from the time when the virtual volume was created or when it was most recently accessed. Time-Delayed Premigration Reference The basis for calculating the time period defined in Time-Delayed Premigration Delay. Possible values are: - Volume Creation
- Calculate premigration delay starting with the time when the virtual volume was created. This refers to the time a write operation was performed from the beginning of a tape -- either a scratch mount or a private mount where writing began at record 0.
- Volume Last Accessed
- Calculate premigration delay starting with the time when the virtual volume was most recently accessed.
Partition Number The partition number for a TS7700 Tape Attach Cluster. Possible values are C0 through C7. "Inserted" logical volumes are those with a -1 partition, meaning that there is no consistent data yet. Storage Preference The priority for removing a virtual volume when the cache reaches a predetermined capacity. Possible values are: - Prefer Remove
- These virtual volumes are removed first when the cache reaches a predetermined capacity and no scratch-ready volumes exist.
- Prefer Keep
- These virtual volumes are the last to be removed when the cache reaches a predetermined capacity and no scratch-ready volumes exist.
- Pinned
- These virtual volumes are never removed from the TS7700 Cluster
Cloud Data Status Status information on the data that is part of a virtual volume in the cloud: - -
- The cluster has no visibility to the cloud.
- No data exists in the cloud
- From the viewpoint of this cluster, the volume does not exist in the cloud (for example, it may not be a TS7700C cluster).
- Data is premigrated in the cloud
- The volume is in disk cache and in the cloud, and is accessible to this cluster.
- Data is migrated in the cloud
- The volume is not in disk cache but is in the cloud, and accessible to this cluster.
- Data is available in the cloud
- This cluster is not set to receive a copy of this volume but has access to it and it is available in the cloud.
Cloud Pool The nickname of the cloud pool. Cloud Account The name of the cloud account Cluster to Premigrate to Cloud The id of the cluster premigrating the volume to the cloud Cloud Consistency Status information regarding cloud storage operations: - Unaware
- This cluster has no visibility to the container where this volume is stored or is not cloud attached.
- Aware
- This cluster is aware of the existence of this object but access and pre-migration has not been attempted.
- Checked
- This cluster is aware of the existence of this object through a previous check. For example, through a pre-migration attempt.