8.1

Table 9‑1. Replication Statuses (Continued)
Status Description Remediation
Error The replication is not running at the
moment.
n
A configuration error occurred.
n
A replication error occurred. For
example, the target site
infrastructure is not accessible.
n
Reconfigure the replication.
n
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.
n
The network connection between the
source and the target site is
dropping intermittently.
n
The bandwidth of the connection
between the source and the target
site is too low.
n
The replication is not running, so
data cannot be replicated on the
target site.
n
Improve the network connection
between the source and target site.
n
Increase the RPO period.
n
For replication status Not Active or
Error, address the cause for the
status and wait for the next sync.
Pause or Resume a Replication
To control the network traffic between the local site and the cloud site, you can pause and resume
replications.
Prerequisites
Verify that you have enough privileges to manage replications. See Roles and Permissions That Disaster
Recovery to Cloud Requires.
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 the site pair to the cloud provider site and click View
Details.
4 Click the Replications tab, click Forward replications or Reverse replications, and select the
replication you want to pause or resume.
vSphere Replication for Disaster Recovery to Cloud
VMware, Inc. 37