The following table provides information pertaining to the Rlink flags used by Volume Replicator. An Rlink represents the actual communication link from the Primary Replicated Volume Group (RVG) to the Secondary RVG.
The following flags are obtained when running the vxprint command for Replicated Data Set (RDS)
| RLINK Flags | Significance and corrective action if required |
|---|---|
| autosync | The RDS is in the process of automatic synchronization. |
| attached | The RLINK is attached to the RVG. |
| can_sync | If the inconsistent and can_sync flags are set, there is enough information in the Secondary SRL volume to make the Secondary consistent again and capable of taking over. |
| cant_sync | The RLINK is inconsistent, and this Secondary needs a complete resynchronization before it can take over or replicate. |
| connected | The RLINK is connected to the corresponding RLINK on the remote host and replication can take place. |
| consistent | The state of the data volumes on the Secondary is suitable for takeover. |
| dcm_logging | DCM is in use (DCM is active for the RVG), due to either autosync, failback sync, or an SRL overflow. It can also be a result of resync-from-replica operation done on volumes associated to the primary RVG. |
| failback_logging | DCM is active for the RVG as a result of FFB takeover. |
| detached | The RLINK is STALE and not taking part in replication. Attach the rlink using vxrlink -a att (autosync attach) or vxrlink -c att (checkpoint attach) command. |
| disconnected | The two RLINKs are not connected and are not replicating. |
| fail | An I/O error occurred while writing to a data volume on the Secondary. |
| inconsistent | The data in the Secondary volumes is not consistent and the Secondary cannot take over. |
| needs_recovery | Rlink is not recovered. Vxrlink recover command should be used to recover the rlink. Vxrvg recover command should be used to recover the corresponding RVG, if this flag is set for the RVG as well. |
| Primary_paused | The Primary RLINK has been paused and replication is not ON. |
| resync_started | The resynchronization of the Secondary has been started. |
| resync_paused | The resynchronization has been started but is not currently active because of some problem. This can typically happen if the rlink disconnects while resynchronization is in progress. |
| secondary_config_err | There is a mismatch between the configuration of the volumes on the Primary and the Secondary - either a volume is missing on the Secondary or its length is not the same as that of the corresponding volume on the Primary. Vxrlink verify command can be used to get details on the exact configuration error. |
| secondary_log_err | An I/O error has occurred on the Secondary SRL; replication cannot continue until the SRL has been dissociated and a new one associated. |
| secondary_paused | The Secondary RLINK has been paused and the replication is not ON. |
| primary / secondary / acting_secondary | Indicates the role of the RVG. |
| enabled / attached | Indicates that I/Os can be performed. |
| disabled / detached | Indicates that I/Os cannot be performed. Vxrvg start command can be used to enable the RVG. |
| enabled/detached | Indicates that RVG is in FAIL state. This happens if there is an I/O error on one or more data volumes associated to the RVG. Correct this error and then start the RVG using vxrvg start command. |
| awaiting_checkend | Indicates that the RVG is checkstarted. |
| passthru | Indicates that the replicator log volume is not associated to the RVG or it is not accessible. |
| needs_recovery | RVG is not recovered, use vxrvg recover command to recover the RVG. |
| srl_header_err | There was an error accessing the replicator log volume associated to the RVG. Correct this error and dissociate and associate the replicator log volume again. |