Home > Storage > PowerStore > Data Protection > Dell PowerStore: Metro Volume > Replication states
This section describes the different major states for a Metro Volume. Some of the following states show more information in parentheses in the UI.
In this state, PowerStore Metro Volume is fully synchronized and active-active. Both sides of the Metro Volume serve host I/O, and a host only receives an acknowledgment from the array when the I/O is committed on both sides of the Metro Volume. Possible sub-states are Active-Active, and Asynchronously Synchronizing when reprotecting starts from a promoted volume.
PowerStore orchestrates the copy and mirror operations. This state only allows host I/O to the preferred or promoted side of a Metro Volume. Possible substates are Asynchronously Synchronizing, and Committing to Active-Active.
The peer PowerStore systems could not synchronize I/O. This state could be caused by an array failure or link failure required for replication. This state only allows host I/O to the preferred or promoted side of a Metro Volume.
In this state, the Metro Volume is paused. The state is triggered by the operation Pause in PowerStore Manager. This state only allows host I/O to the preferred or promoted side of a Metro Volume.
This is a transient state after you resume a paused Metro Volume and trigger the state Switching to Active-Active. This state only allows host I/O to the preferred or promoted side of a Metro Volume.
This state indicates that PowerStore initiated the Metro Volume self-healing recovery for Metro Sync replication to return to the active-active state. This state only allows host I/O to the preferred or promoted side of a Metro Volume.
Replication is in this state when it is swapping the roles of preferred and non-preferred volumes of metro sync session.
This state occurs after a Metro Volume is being unconfigured after an End Metro Volume state in PowerStore Manager.