You can monitor the status of your replications, view information about the virtual machines configured for replication, or get a remediation plan for some replication states.

For more information about how to identify replication errors, see Identifying Replication Problems.

Prerequisites

  • Verify that vSphere Replication is running.
  • Verify that the virtual machines are configured for replication.

Procedure

  1. Log in to the vSphere Client or vSphere Web Client.
  2. On the home page, click Site Recovery and click Open Site Recovery.
  3. On the Site Recovery home page, select a site pair and click View Details.
  4. To see details of the virtual machines replicated from this site, select the Replications tab and click Outgoing or Incoming.
    Table 1. Replication Statuses
    Status Description Remediation
    OK The replication is running. Not needed.
    Not Active

    The replication is not running at the moment.

    • The source virtual machine is powered off.
    • A communication problem might have occurred between the source ESXi host and the target site.
    • At target site, the vSphere Replication server cannot access the datastore using an ESXi host.
    • Power on the source virtual machine.
    • Check the network connectivity between source and target site.
    Paused

    The replication is not running at the moment. A vSphere Replication user has paused the replication.

    		From the list of replications, select the paused replication and click the Resume icon.
    Error

    The replication is not running at the moment.

    • A configuration error occurred.
    • A replication error occurred. For example, the target site infrastructure is not accessible.
    • Reconfigure the replication.

    • Verify whether some problem occurred on the virtual machine by clicking the Site Pair tab and clicking Issues.

    Status (RPO violation)

    For replication status OK, Sync, or Full Sync, the replication is running, but the RPO that is set for the replication is not met and is violated.

    For replication status Not Active or Error, the replication is not running, and the RPO that is set for the replication is violated.

    • The network connection between the source and the target site is dropping intermittently.
    • The bandwidth of the connection between the source and the target site is too low.
    • The replication is not running, so data cannot be replicated on the target site.
    • Improve the network connection between the source and target site.
    • Increase the RPO period.
    • For replication status Not Active or Error, address the cause for the status and wait for the next sync.
    Note: If a replication is in the Not Active replication state, you might have connected the source and target sites using network address translation (NAT). vSphere Replication does not support NAT. Use credential-based authentication and network routing without NAT when connecting the sites. Another cause for a Not Active replication state might be that the source virtual machine is powered off. Automatic replication works only on virtual machines that are powered on.