5.5
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
- Configure Replication for Multiple Virtual Machines
- Move a Virtual Machine to a New vSphere Replication Server
- Stop Replicating a Virtual Machine
- Reconfiguring Replications
- 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 Disconnected 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
You can also use the PIT instances to recover the last known good state of a database.
Note vSphere Replication does not replicate virtual machine snapshots.
Figure 8‑1. Recovering a Virtual Machine at Points in Time (PIT)
vSphere Web Client
VR Appliance
t1
VM
VM VM VM
t3t2
vSphere Web Client
VR Appliance
VM
Replication
Source Site
Target Site
t0
Using vSphere Replication with Virtual SAN Storage
You can use VMware Virtual SAN datastores as a target datastore when configuring replications. Follow
the guidelines when using vSphere Replication with Virtual SAN storage.
Note VMware Virtual SAN is a fully supported feature of vSphere 5.5u1.
n
You can use Virtual SAN in production environments with vSphere Replication 5.5.1 and vSphere
5.5u1.
n
Virtual SAN is an experimental feature in vSphere 5.5. You can perform testing with Virtual SAN with
vSphere Replication 5.5.0 and vSphere 5.5, but it is not supported for use in production
environments. See the release notes for the vSphere Replication 5.5.0 release for information about
how to enable Virtual SAN in vSphere 5.5.
vSphere Replication does not support replicating or recovering virtual machines to the root folders with
user-friendly names on Virtual SAN datastores. These names can change, which causes replication
errors. When selecting Virtual SAN datastores, always select folders with UUID names, which do not
change.
Configuring Replications
When configuring replications for a single virtual machine, vSphere Replication creates the destination
folder that you choose, obtains the UUID reference for that folder, and then uses the UUID name rather
than the user-friendly name. The UUID name is visible when vSphere Replication displays the target
folders when reconfiguring replications.
When configuring replication for multiple virtual machines, create a root folder in the Virtual SAN
datastore, obtain its UUID name, and use the folder that is identified by the UUID in the replication wizard.
Configure vSphere Replication on batches of a maximum of 30 virtual machines at a time.
VMware vSphere Replication Administration
VMware, Inc. 58