acting_secondary

This Primary RVG is currently the acting Secondary as part of the fast failback process. Writes to the data volumes in this RVG are disabled independent of whether the RVG is started or stopped.

disabled for I/O

Primary RVG is disabled for I/O, that is, the RVG is stopped.

enabled for I/O

Primary RVG is enabled for I/O, that is, RVG is started.

needs recovery

State after an import or reboot.

passthru

The Primary RVG is in passthru mode because the Primary SRL is detached or missing.

consistent, behind

Secondary data is consistent but not up-to-date with the Primary data.

consistent, stale

The data on this Secondary is consistent. Replication to this Secondary has been stopped; the Primary RLINK is detached.

consistent, up-to-date

The Secondary data is consistent and is current or up-to-date with the Primary data. The Primary role can be migrated to this Secondary.

inconsistent

The data on the Secondary volumes is not consistent and the Secondary cannot take over.

needs recovery

State after an import or reboot.

The vxrlink recover command clears this state.

N/A

Current state of the Secondary data cannot be determined. This may occur because of a configuration error on this Secondary.

logging to DCM

DCM is active for this Secondary, that is, new updates on Primary are tracked using DCM for this Secondary. The following information may be displayed:

needs failback synchronization

This Primary RVG is acting as Secondary as part of the fast failback process. To continue replication, start failback resynchronization on the new Primary.

not replicating

Data is not being replicated to Secondary because Primary RLINK is in needs_recovery state.

paused by user

Replication to Secondary is paused because of some administrative action. This results in the following states:

primary paused - Primary RLINK is paused.

secondary paused - Secondary RLINK is paused.

paused due to error

Replication to Secondary is paused because of the following errors:

paused due to network disconnection

Replication to Secondary is paused because of some network problem.

replicating

connected - Replication can take place if there are updates on the Primary data volumes

resync in progress

Resynchronization to the Secondary is in progress.

autosync - Resynchronization type is autosync.

dcm resynchronization - Resynchronization after an SRL overflow.

failback resynchronization - Resynchronization using failback logging.

resync paused by user

Resynchronization to Secondary is paused because of some administrative action. This results in the following states:

resync paused due to error

Resynchronization to Secondary is paused because of the following errors:

resync paused due to network disconnection

Resynchronization to Secondary is paused because of some network problem.

stopped

Replication to Secondary is stopped because of the following:

N/A

The replication status cannot be determined.

DCM (contains xxx Kbytes) (log_type)

DCM is active (in use) for the replication to this Secondary. log_type can be autosync, failback logging, or SRL protection logging.

SRL (xxx Kbytes behind, yyy % full)

Updates to be transferred to Secondary are logged into the SRL and are currently occupying xxx Kbytes or yyy% of the SRL

SRL

SRL is used for logging. Check the Data status field for the status of the Secondary data.

host: Pri or Sec IP not available or vradmind not running

The Primary IP or the Secondary IP address is not available, or the vradmind daemon on the host is not running or is running on a different port.

host: disk group missing.

Host host does not have any disk group with the same name as that specified in the remote_dg attribute, of the Primary RLINK pointing to this host.

host: RLINK missing.

Primary RVG has an RLINK to host, but host does not have corresponding rlink to this Primary RLINK.

host: RLINK dissociated.

Host host does have an RLINK corresponding to the Primary RLINK. However, it is not associated with the Secondary RVG.

host: disk-group mismatch.

The remote_dg attribute of either the Primary RLINK or Secondary RLINK is incorrect.

host: RLINK mismatch.

The remote_rlink attribute of either the Primary RLINK or Secondary RLINK is incorrect.

host: host mismatch.

The local_host and/or remote_host attribute of either the Primary RLINK or Secondary RLINK is incorrect.

host: Primary-Primary configuration.

The two Primary RVG RLINKs are pointing to each other. This situation will arise after the original Primary comes up after a Primary failover.

host: multiple Primary error.

The same Secondary RVG has more than one Primary RVGs.

host: two or more nodes on same host.

Two or more RVGs in the same RDS are located on the same host, host. This configuration is not supported.

No Primary RVG.

Ignore this error if it displays only for a few seconds and disappears. If the error persists, then the problem may be due to the Secondary not being able to determine its Primary because it has some configuration error, the Primary is not reachable, or it does not have any RLINK.

host: Primary and Secondary have same disk-group ID.

This condition happens in the cases when the split mirrored plexes of the Primary volumes are exported without using the Disk Group split option and then imported on the Secondary with force option.

host: unknown

The configuration status is currently unknown.

host: stale information

The configuration status may be stale.

host: no data volume

This error can occur if one of the RVGs in the RDS does not have a data volume associated with it.

host: network-protocol mismatch

The protocol attribute of the Primary RLINK is different from that of the Secondary RLINK.

host: VVR-heartbeat-port mismatch

The local_port attribute setting for the Primary RLINK is different from that of the Secondary RLINK.

host: unsupported VVR version in cross-version replication

The cross-version replication in VVR is only supported between two immediate major releases.

host: no contact from Primary

This error can occur if the vradmind server on the Secondary host is unable to establish contact with the vradmind server on the Primary. This can be because the Primary RVG of this RDS cannot be found or the vradmind server is not running or is unreachable.

host: vxconfigd disabled

The vxconfigd daemon is currently disabled on the host on which this error occurred.

host: volume-number mismatch

This error can occur if the number of volumes in the Primary and Secondary RVGs of the RDS are different.

host: volume-size mismatch

This error can occur if the sizes of some or all of the data volumes in the Primary and Secondary RVGs of the RDS do not match.

host: volume-name mismatch

This error can occur if some or all of the volumes in the Primary and Secondary RVGs of the RDS are not mapped correctly.

host: Primary SRL missing

This error can occur if the Primary SRL was disassociated from the Primary RVG or is missing.

host: Secondary SRL missing

This error can occur if the Secondary SRL was disassociated from the Secondary RVG or is missing.