CLI Guide

Table 16. virtual-volume field descriptions (continued)
Field Description
expandable-capacity
Excess capacity not yet exposed to the host by the virtual
volume. This capacity is available for expanding the virtual
volume.
● Zero (0) - Expansion is not supported on the virtual
volume or that there is no capacity available for expansion.
● Non-zero - The capacity available for virtual volume
expansion using the storage-volume method.
expansion-method
The expansion method that can be used to expand the virtual
volume.
● concatenation - The virtual volume can be expanded
only by adding the specified extents.
● not-supported - The virtual volume cannot be
expanded. This includes virtual volumes that are members
of RecoverPoint consistency groups.
● storage-volume - The virtual volume can be expanded
using storage array based volume expansion or by
migrating to a larger device.
expansion-status
Expansion status for the volume.
● - - None of the other expansion states apply. No operation
is blocked by this state.
● failed - An expansion has failed. The expansion has
failed and the expansion must be re-tried. If the expansion
is not retried this state will persist for up-to 2 days. See
health-indications for more information.
● When an expansion fails, the overall health, operational-
status, or service-status of the virtual-volume is not
degraded.
● in-progress - An expansion has been started, but has
not completed. The following operations are blocked on
the volume: additional expansion, migration, and NDU.
● unknown - Metro node could not determine the expansion
status of the volume.
health-indications
Indicates the reasons for:
● A health-state that is not 'ok'
● The reasons for the failure of virtual volume expansion or
initialization.
health state
● major failure - One or more of the virtual volume's
underlying devices is out-of-date, but will never rebuild.
● minor failure - One or more of the virtual volume's
underlying devices is out-of-date, but will rebuild.
● non-recoverable error - Metro node cannot
determine the virtual volume's Health state.
● ok - The virtual volume is functioning normally.
● unknown -Metro node cannot determine the virtual
volume's Health state, or the state is invalid.
initialization-status
Status of the initialization process on the virtual volume.
● success - Indicates that the initialization process is
completed successfully.
● failed - Indicates that the initialization process is failed.
● in-progress - Indicates that the initialization process is
in progress.
● unknown - Indicates that the initialization process remains
in a status other than success, failed, or in-
progress.
328 Commands