6.5
Table Of Contents
- Using VMware vSphere Replication
- Contents
- About Using VMware vSphere Replication
- Replicating Virtual Machines
- How the Recovery Point Objective Affects Replication Scheduling
- How the 5 Minute Recovery Point Objective Works
- How Retention Policy Works
- Replicating a Virtual Machine and Enabling Multiple Point in Time Instances
- Using vSphere Replication with Virtual SAN Storage
- Using vSphere Replication with vSphere Storage DRS
- How vSphere Replication Synchronizes Data Between vCenter Server Sites During Initial Configuration
- Replicating Virtual Machines Using Replication Seeds
- Replicating a Virtual Machine in a Single vCenter Server Instance
- Best Practices For Using and Configuring vSphere Replication
- Configure Replication for a Single Virtual Machine to vCenter Server
- Configure Replication for Multiple Virtual Machines to vCenter Server
- Move a Replication 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 Point in Time Settings of a Replication
- Change the Target Datastore Location of a Replication
- Monitoring and Managing Replications in vSphere Replication
- Performing a Recovery with vSphere Replication
- Troubleshooting vSphere Replication
- Generate vSphere Replication Support Bundle
- 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
- 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 Operations Fail with Authentication Error
- 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
- Configuring Replication Fails Because Another Virtual Machine has the Same Instance UUID
- Not Active Replication Status of Virtual Machines
- 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
- Unable to Establish an SSH Connection to the vSphere Replication Appliance
- The Replication Pauses When You Add a New Disk To the Source VM
- The vSphere Replication Appliance Root File System Switches to Read-only Mode and Login Fails
4 Resize the disk of the recovered virtual machine on the target site.
5 Unregister the recovered virtual machine on the target site, but do not delete the disks.
6 Configure replication by using the disks of the recovered virtual machine as seeds.
Change the Point in Time Settings of a Replication
You can reconfigure a replication to enable or disable the saving of point in time instances, or to change
the number of instances that vSphere Replication keeps.
vSphere Replication can save replication instances that can be used as snapshots after recovery or
planned migration operations. You can save up to 24 point in time instances per VM.
Procedure
1 On the vSphere Replication Home page, click the Monitor tab, and click Outgoing Replications.
2
Select the replication that you want to reconfigure and click the Reconfigure replication icon , or
right-click the replication source virtual machine and select All vSphere Replication Actions >
Reconfigure.
The reconfiguration wizard opens. You might be prompted to provide login credentials for the target
site.
3 Click Next until you reach the Recovery settings page of the wizard.
4 In the Point in time instances pane, make the changes that you want to apply and click Next.
Action Procedure
Enable the saving of point in time
instances
Select the Enable check box.
Disable the saving of point in time
instances
Deselect the Enable check box.
Adjust the number of instances to keep Use the spin-boxes to adjust the number of instances to keep per day and the
number of past days for which you want to keep replication instances.
Note You cannot keep more than 24 replication instances per virtual machine.
5 Click Finish to save your changes.
If you selected to disable the saving of point in time instances, the instances that exist on the target site
are deleted when the next replication instance appears on the target site. The moment when a new
replication instance is saved on the target site depends on the RPO setting.
Using VMware vSphere Replication
VMware, Inc. 24