Understanding Replication Status

The Group Manager GUI displays the status of individual replicas, in addition to replication operations. The status may depend on whether the view is from the primary group or the secondary group.

Each replica is identified by the date and time the replication operation started.

Table 1: Replica Status shows the possible replica statuses. Note that, from the view of the primary group, a replica status can also be one of the replication operation statuses described in Table 2: Replication Operation Status – Primary Group.

Table 1: Replica Status

Status

Description

complete

All volume data has been stored on the secondary partner.

incomplete or in-progress

Replication is not complete.

manual-in-progress

Manual transfer replication is in progress, and you may need to perform additional tasks to complete the process. (In this case, an action item appears in the Outstanding Alarms panel at the bottom of the GUI.)

paused

Replication was paused

ready

Volume is not currently being replicated.

Possible values for replication operation status, as seen from the primary group, are shown in Table 2: Replication Operation Status – Primary Group.

Table 2: Replication Operation Status – Primary Group

Status

Description

auth-failure

Authentication between the partners failed.

Note: Check the passwords configured on the partners.

cancelling

Administrator cancelled the replication operation.

completed

The last replication completed successfully.

disabled

Replication of the volume has been manually disabled.

enabled

Volume is enabled for replication.

failed

Volume replication has failed.

Note: Check the event log to determine why the replication operation failed.

in-progress

Volume is currently being replicated to the partner.

manual-in-progress

Manual transfer is currently in progress.

paused

Replication of the volume has been manually paused.

partner-down

Volume replication cannot proceed because the partner cannot be reached.

Note: Check the network link between partners.

partner-needs-upgrade

Replication has been paused automatically because the partner is running incompatible firmware and must be upgraded to the same firmware as the group. Replication will resume automatically when the partner is upgraded.

partner-paused-outbound

Partner administrator paused outbound replication.

partner-paused-inbound

Partner administrator paused inbound replication.

paused

Administrator paused replication to the partner.

paused-max-snap-reached

Volume replication paused because the partner (secondary group) has reached the maximum number of replicas or snapshots for a group.

Note: To continue the replication, you must delete replicas or snapshots. If a schedule is being used to create replicas, you may want to decrease the maximum number of replicas to keep.

paused-partner-allows-
downgrades

Replication has been paused automatically because the partner group needs to disallow firmware downgrades before replication can resume.

paused-remote-reserve-low

Volume replication was paused because the administrator of the primary group must increase the replica reserve. An event message will display the amount to which the replica reserve must be increased in order for the replication to complete.

Note: See Configuring a Volume or Volume Collection for Replication for information about increasing the replica reserve.

paused-remote-resize-failed

Volume reserve was increased, but the corresponding replica reserve resize operation on the partner failed due to lack of delegated space.

Because replica reserve is based on a percentage of volume reserve, when the volume reserve increases either manually or automatically (for thin provisioned volumes), the replica reserve requirement automatically increases.

Note: To continue replication, the partner group’s administrator must increase the delegated space, as described in Modifying a Replication Partner.

ready

Replication of the volume is not currently in progress.

waiting

Volume replication data transfer has not yet started because the maximum number of in-use replication iSCSI sessions has been reached.

Possible values for replication operation status, as seen from the secondary group, are shown in Table 3: Replication Status – Secondary Group.

Table 3: Replication Status – Secondary Group

Status

Description

auth-failure

Authentication between the partners failed.

Note: Check the passwords configured on the partners.

far-end-down

No communication with the primary group for 1 hour or more, possibly due to a network problem or a failure at the primary group.

incomplete

Replication is not complete.

ready

Volume is not currently being replicated.

stopped

Replication was paused.