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
The number of replication instances that vSphere Replication keeps depends on the configured
retention policy, but also requires that the RPO period is short enough for these instances to be
created. For example, if you set vSphere Replication to keep 6 replication instances per day, the RPO
period should not exceed 4 hours, so that vSphere Replication can create 6 instances in 24 hours.
12 Click Next.
13 On the Ready to complete page, review the replication settings, and click Finish.
vSphere Replication starts an initial full synchronization of the virtual machine files to the designated
datastore on the target site.
Configure Replication for Multiple Virtual Machines to
vCenter Server
To configure batches of virtual machines for replication from one vCenter Server instance to another, you
can select multiple virtual machines and start the Configure Replication wizard.
When you configure replication, you set a recovery point objective (RPO) to determine the period of time
between replications. For example, an RPO of 1 hour seeks to ensure that a virtual machine loses the
data for no more than 1 hour during the recovery. For smaller RPO values, less data is lost in a recovery,
but more network bandwidth is consumed keeping the replica up to date.
Every time that a virtual machine reaches its RPO target, vSphere Replication records approximately
3800 bytes of data in the vCenter Server events database. If you set a low RPO period, this can quickly
create a large volume of data in the database. To avoid creating large volumes of data in the
vCenter Server events database, limit the number of days that vCenter Server retains event data. See
Configure Database Retention Policy in the vCenter Server and Host Management Guide. Alternatively,
set a higher RPO value.
vSphere Replication guarantees crash consistency amongst all the disks that belong to a virtual machine.
If you use VSS quiescing, you might obtain a higher level of consistency. The available quiescing types
are determined by the virtual machine's operating system. See Compatibility Matrixes for vSphere
Replication 5.8 for Microsoft Volume Shadow Copy Service (VSS) quiescing support for Windows virtual
machines.
You can use vSphere Replication with a Virtual SAN datastore on the source and target sites. See Using
vSphere Replication with Virtual SAN Storage for the limitations when using vSphere Replication with
Virtual SAN.
Note VMware Virtual SAN is a fully supported feature of vSphere 5.5u1 and later.
Configuring vSphere Replication on a large number of virtual machines simultaneously when using Virtual
SAN storage can cause the initial full synchronization of the virtual machine files to run very slowly. Initial
full synchronization operations generate heavy I/O traffic and configuring too many replications at the
same time can overload the Virtual SAN storage. Configure vSphere Replication on batches of a
maximum of 30 virtual machines at a time.
VMware vSphere Replication Administration
VMware, Inc. 59