5.8
Table Of Contents
- VMware vSphere Replication Administration
- Contents
- vSphere Replication Administration
- Updated Information
- Overview of VMware vSphere Replication
- vSphere Replication Roles and Permissions
- vSphere Replication System Requirements
- Installing vSphere Replication
- Deploying Additional vSphere Replication Servers
- Upgrading vSphere Replication
- Reconfigure the vSphere Replication Appliance
- Reconfigure General vSphere Replication Settings
- Change the SSL Certificate of the vSphere Replication Appliance
- Change the Password of the vSphere Replication Appliance
- Change Keystore and Truststore Passwords of the vSphere Replication Appliance
- Configure vSphere Replication Network Settings
- Configure vSphere Replication System Settings
- Reconfigure vSphere Replication to Use an External Database
- Use the Embedded vSphere Replication Database
- Replicating Virtual Machines
- How the Recovery Point Objective Affects Replication Scheduling
- Replicating a Virtual Machine and Enabling Multiple Point in Time Instances
- Using vSphere Replication with Virtual SAN Storage
- Replicating Virtual Machines Using Replication Seeds
- Replicating a Virtual Machine in a Single vCenter Server Instance
- Configure Replication for a Single Virtual Machine to vCenter Server
- Configure Replication for Multiple Virtual Machines to vCenter Server
- Move a Virtual Machine to a New vSphere Replication Server
- Stop Replicating a Virtual Machine
- Reconfiguring Replications
- Reconfigure Recovery Point Objectives (RPO) in Replications
- Resize the Virtual Machine Disk Files of a Replication that Uses Replication Seeds
- Resize Virtual Machine Disk Files of a Replication that Does Not Use Replication Seeds
- Change the Target Datastore Location
- Change the Point in Time Settings of a Replication
- Performing a Recovery with vSphere Replication
- Monitoring and Managing Replications in vSphere Replication
- Troubleshooting vSphere Replication
- vSphere Replication Limitations
- Access the vSphere Replication Logs
- vSphere Replication Events and Alarms
- Solutions for Common vSphere Replication Problems
- Error at vService Bindings When Deploying the vSphere Replication Appliance
- OVF Package is Invalid and Cannot be Deployed
- Connection Errors Between vSphere Replication and SQL Server Cannot be Resolved
- Application Quiescing Changes to File System Quiescing During vMotion to an Older Host
- Configuring Replication Fails for Virtual Machines with Two Disks on Different Datastores
- vSphere Replication Service Fails with Unresolved Host Error
- Scalability Problems when Replicating Many Virtual Machines with a Short RPO to a Shared VMFS Datastore on ESXi Server 5.0
- vSphere Replication Sites Appear in the Not Authenticated State
- Error Recovering Virtual Machine in a Single vCenter Server Instance
- vSphere Replication RPO Violations
- vSphere Replication Appliance Extension Cannot Be Deleted
- vSphere Replication Does Not Start After Moving the Host
- Unexpected vSphere Replication Failure Results in a Generic Error
- Increase the Memory of the vSphere Replication Server for Large Deployments
- Reconnecting Sites Fails If One Of the vCenter Servers Has Changed Its IP Address
- Uploading a Valid Certificate to vSphere Replication Results in a Warning
- vSphere Replication Server Registration Takes Several Minutes
- Generating Support Bundles Disrupts vSphere Replication Recovery
- vSphere Replication Operations Take a Long Time to Complete
- vSphere Replication Does Not Display Incoming Replications When the Source Site is Inaccessible
- vSphere Replication is Inaccessible After Changing vCenter Server Certificate
- vSphere Replication Cannot Establish a Connection to the Hosts
- Anti-virus Agent in Firewall Terminates Virtual Machine Replication
- Initial Full Synchronization of Virtual Machine Files to VMware Virtual SAN Storage Is Slow
- vSphere Web Client 5.1.x Non-Functioning Option Binds vSphere Replication Traffic to a Specific vmknic
- Configuring Replication Fails After Rebuilding VRMS
- vSphere Replication Operations Run Slowly as the Number of Replications Increases
- Error at Reconfiguring the vSphere Replication Management Server from the Virtual Appliance Management Interface
Interpreting Replication Statistics for a Site
You can use the reports that vSphere Replication compiles to optimize your environment for replication,
identify problems in your environment, and reveal their most probable cause.
Server and site connectivity, number of RPO violations, and other metrics give you, as an administrator,
the information you need to diagnose replication issues.
The following sections contain examples of interpreting the data displayed under Reports on the
vSphere Replication tab under Monitor.
RPO Violations
The large number of RPO violations can be caused by various problems in the environment, on both the
source and the target site. With more details on historical replication jobs, you can make educated
decisions on how to manage the replication environment.
Table 10‑2. Analysing RPO Violations
Probable Cause Solution
n
The network bandwidth cannot accommodate all
replications.
n
The replication traffic might have increased.
n
The initial full sync for a large virtual machine is taking
longer than the configured RPO for the virtual machine.
n
Disable the replication on some virtual machines with high
change rate to allow lower change rate virtual machines to
meet their RPO objectives.
n
Increase the network bandwidth for the selected host.
n
Check if the replication traffic has increased. If the traffic has
increased, investigate possible causes, for example the
usage of an application might have changed without you
being informed.
n
Check the historical data for average of transferred bytes for
a notable and sustained increase. If an increase exists,
contact application owners to identify recent events that
could be related to this increase.
n
Adjust to a less aggressive RPO or look at other ways to
increase bandwidth to accommodate the current RPO
requirements.
n
A connectivity problem exists between the source and the
target site.
n
An infrastructure change might have occurred on the target
site.
n
Check the site connectivity data to verify the connection
between the source and target site.
n
Check if the infrastructure on the target site has changed or
is experiencing problems that prevent vSphere Replication
from writing on the target datastores. For example, storage
bandwidth management changes made to target hosts
might result in storage delays during the replication process.
n
Check on the vSphere Replication Management Server
appliance and the vSphere Replication Server appliance.
Someone might have shut down the appliance or it might
have lost connection.
VMware vSphere Replication Administration
VMware, Inc. 72