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
Configuring Replications by Using Replication Seeds
When copying replication seed files to the target datastore, you can use the vSphere Web Client to create
a new root folder on a Virtual SAN datastore, or place the files in an existing folder. When you configure
replications that use replication seeds, you must select the folder by using its UUID name. Selecting the
user-friendly folder names is not supported.
Reconfiguring Replications
If you want to change the destination folder for a disk or the virtual machine config files, you must use the
following options:
n
Select the UUID name of an existing folder.
n
Allow vSphere Replication to create a new folder and obtain its UUID name.
Limits of Using vSphere Replication with Virtual SAN Storage
For reasons of load and I/O latency, Virtual SAN storage is subject to limits in terms of the numbers of
hosts that you can include in a Virtual SAN cluster and the number of virtual machines that you can run
on each host. See the Limits section in the VMware Virtual SAN Design and Sizing Guide at
http://www.vmware.com/products/virtual-san/resources.html.
Using vSphere Replication adds to the load on the storage. Every virtual machine generates regular read
and write operations. Configuring vSphere Replication on those virtual machines adds another read
operation to the regular read and write operations, which increases the I/O latency on the storage. The
precise number of virtual machines that you can replicate to Virtual SAN storage by using
vSphere Replication depends on your infrastructure. If you notice slower response times when you
configure vSphere Replication for virtual machines in Virtual SAN storage, monitor the I/O latency of the
Virtual SAN infrastructure. Potentially reduce the number of virtual machines that you replicate in the
Virtual SAN datastore.
Retaining Point-in-Time Snapshots when Using Virtual SAN
Storage
Virtual SAN storage stores virtual machine disk files as a set of objects and components. Each disk object
in Virtual SAN storage has mirror and witness objects. In the default Virtual SAN storage policy, a disk
object has 2 mirrors and one witness. The number of mirror components is determined by the size of the
virtual machine disk and the number of failures to tolerate that you set in your Virtual SAN storage policy.
A mirror object is divided into components of a maximum size of 256 GB each.
n
If a virtual machine has one 256 GB disk and you use the default Virtual SAN storage policy, the disk
object will have 2 mirror components of 256 GB each and 1 witness, to make a total of 3 components.
n
If a virtual machine has one 512 GB disk and you use the default Virtual SAN storage policy, the disk
object will have 4 mirror components of 256 GB each and 1 witness, to make a total of 5 components.
VMware vSphere Replication Administration
VMware, Inc. 55