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
3 Select a vSphere Replication Server from the list, and click OK.
The newly assigned server is updated in the vSphere Replication Server column.
Stop Replicating a Virtual Machine
If you do not need to replicate a virtual machine, you can stop the replication of that virtual machine.
Take a note of the target datastore and the name of the replication that you are about to stop. You need
this information to clean up your environment after you stop the replication.
Prerequisites
Verify that you are logged in the vSphere Web Client as a VRM virtual machine replication user or a VRM
administration user. For more details, see vSphere Replication Roles Reference in the
vSphere Replication Installation and Configuration guide.
Procedure
1 In the vSphere Replication Home page, go to the Monitor tab and click Incoming Replications or
Outgoing Replications.
2 Right-click a replication and select Stop.
vSphere Replication asks you if you want to permanently stop the replication for the selected virtual
machine.
Note The hosts and vSphere Replication server used by the replication must be accessible to stop a
replication on both sites. If a host or the server is not accessible, you can force stop the replication on
the accessible site by selecting Force stop replication. If you force stop the replication from
Incoming Replications, you must also force stop the corresponding replication from Outgoing
Replications if the source site is available. If you force stop the replication from Outgoing
Replications, you can only recover or force stop the corresponding replication from Incoming
Replications.
3 Click Yes to confirm that you want to stop replicating this virtual machine.
The virtual machine does not replicate to the target site.
Using VMware vSphere Replication
VMware, Inc. 21