< Previous  | TOC | Index | Next  >

Displaying consolidated replication status

The vradmin repstatus command displays the consolidated replication status of the specified Replicated Data Set (RDS). The vradmin repstatus command displays the following information about each RVG in the RDS:

• Consolidated view of the RDS
• Replication settings for all Secondary hosts in the RDS
• Status of the data on each Secondary host in the RDS
• Status of replication to each Secondary host in the RDS

To display consolidated replication information about an RDS:

# vradmin -g diskgroup [-l] repstatus local_rvgname

The argument local_rvgname is the name of the RVG on the local host. The local RVG name represents its RDS.

The option -l displays additional information, such as RLINK names, replication setting, and so on. Similar to the vradmin -l printrvg command, the vradmin repstatus command also displays configuration errors in the RDS, if any.

  Note   If the vradmin repstatus command is run on a Secondary that has a few configuration errors or cannot reach the Primary, the output displays the status known to the Secondary before the above condition occurred and therefore might be out of date.

Example:

When the Primary is reachable from all the Secondary hosts and the
vradmin repstatus command is run from any host:

# vradmin -g hrdg -l repstatus hr_rvg

Output resembles:

Replicated Data Set: hr_rvg

Primary:

Host name:  seattle

RVG name:  hr_rvg

DG name:  hrdg

RVG state:  enabled for I/O

Data volumes:  4

  Vsets:                     1

SRL name:  hr_srl

SRL size:  4.00 GB

Total secondaries:         1

Secondary:

Host name:  london

RVG name:  hr_rvg

DG name:  hrdg

Rlink from Primary:  rlk_london_hr_rvg

Rlink to Primary:  rlk_seattle_hr_rvg

Configured mode:  asynchronous

Latency protection:  off

SRL protection:   autodcm

Data status:               inconsistent

Replication status:        resync in progress (autosync)

Current mode:              asynchronous

Logging to:                DCM (contains 169728 Kbytes) (autosync)

  Timestamp Information: N/A

Bandwidth Limit: 30.00 Mbps

Example:

When the Primary is unreachable from the Secondary hosts and the
vradmin repstatus command is run from the Secondary host:

# vradmin -g hrdg -l repstatus hr_rvg

Output resembles:

VxVM VVR vradmin INFO V-5-52-1205 Primary is unreachable or RDS has configuration
error. Displayed status information is from Secondary and can be out-of-date.

Replicated Data Set: hr_rvg

Primary:

Host name: seattle <unreachable>

RVG name: hr_rvg

DG name: hrdg

RVG state: enabled for I/O

Data volumes: 4

Vsets:                      1

SRL name: hr_srl

SRL size: 4.00 GB

Total secondaries: 1

Secondary:

Host name: london

RVG name: hr_rvg

DG name: hrdg

Rlink from Primary: rlk_london_hr_rvg

Rlink to Primary: rlk_seattle_hr_rvg

Configured mode: asynchronous

Latency protection: off

SRL protection: autodcm

Data status: consistent, up-to-date

Replication status: replicating (connected)

Current mode: asynchronous

Logging to: SRL (0 updates behind, last update ID 18533.0)

Timestamp Information: behind by 00:00:00 hours

Bandwidth Limit: 30.00 Mbps

Last Update on Primary: Oct 10 04:32:21

Secondary up-to-date as of: Oct 10 04:32:21

Config Errors:

seattle: Pri or Sec IP not available or vradmind not running,
stale information

The following section describes the important fields displayed by the vradmin repstatus command. The values and meaning of each field are listed in tables:

• RVG state: Displays the state of the Primary RVG. The following table lists the values for the RVG state field and their meanings.

   

  Value	Meaning
  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. The vxrvg recover rvg command clears this state.
  passthru	The Primary RVG is in passthru mode because the Primary SRL is detached or missing. For more information, see RVG PASSTHRU mode.

• Data status: Shows the data status of this Secondary. The following table lists the values for the Data status field and their meanings:

   

  Value	Meaning
  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. For information about the state, use the vxprint -l rlink_name command on the Primary and Secondary.

• Current mode: Displays the mode of replication, asynchronous or synchronous, that is being used to replicate data to the Secondary. This value can be different from the configured replication setting if the configured mode is synchronous=override. For more information, see Changing the replication settings for a Secondary.
• Replication status: Displays the status of the replication to the Secondary. The following table lists the values for the Replication status field and their meanings:

   

  Value	Meaning
  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 dcm resynchronization—To continue replication, resynchronize the Secondary using DCM resynchronization. See Incrementally synchronizing the Secondary after SRL overflow.  needs failback synchronization—To continue replication, start failback synchronization to this Secondary. See Failing back using fast failback synchronization.
  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.  primary needs_recovery—Primary RLINK in needs_recovery state and needs to be recovered before replication can resume.
  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:  secondary config error—Secondary has some configuration error. For more information, refer to the secondary_config_err in the section Interpreting RLINK flag settings.  secondary log error—Secondary SRL has an I/O error. See the secondary_log_err in section Interpreting RLINK flag settings.
  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:   primary paused—Primary RLINK is paused.  secondary paused—Secondary RLINK is paused.
  resync paused due to error	Resynchronization to Secondary is paused because of the following errors:  secondary config error—Secondary has some configuration error. For more information, refer to the secondary_config_err in the section Interpreting RLINK flag settings.  secondary log error—Secondary SRL has an I/O error. See the secondary_log_err in section Interpreting RLINK flag settings.
  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:  Primary detached—Primary RLINK is detached.  Secondary detached—Secondary RLINK is detached.
  N/A	The replication status cannot be determined. For information about the status, use the vxprint -l rlink_name command on the Primary and Secondary.

• Logging to: Indicates whether updates for this Secondary are tracked on the Primary using the SRL or DCM. The following table lists the values for the Logging to field and their meanings:

   

  Value	Meaning
  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.

  If the vradmin repstatus command is run on a Secondary and the Secondary is disconnected from the Primary because of a configuration or network error, the Logging to field may show the following values:

   

  Value	Meaning
  DCM (log_type)	The last known information about logging type before the Secondary disconnected from the Primary is that it was logging to DCM.
  SRL (xxx updates behind, last update ID yyy)	Before Secondary disconnected from the Primary, SRL was used for logging. Secondary was xxx updates behind the Primary, and the last update that was applied on the Secondary has update ID yyy. This information is similar to that displayed by the vxrlink updates command.
  SRL (updates behind N/A)	Before Secondary disconnected from the Primary, SRL was used for logging. The number of updates this Secondary is behind with the Primary is not known.

• Timestamp information, Last Update on Primary, Secondary up-to-date as of:

  These fields are the same as the output that is displayed for the vxrlink -T command. For more information, see Displaying the status of a Secondary and Identifying the most up-to-date Secondary.