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
Performing a Recovery with
vSphere Replication 9
With vSphere Replication, you can recover successfully replicated virtual machines at the target site.
vSphere Replication performs a sequence of steps to recover replicated virtual machines.
n
If you perform a synchronization of the latest changes, vSphere Replication checks that the source
site is available and source virtual machine is powered off before recovering the virtual machine on
the target site. Then vSphere Replication synchronizes the changes from the source to the target site.
n
If you skip synchronization and recover with the latest data available (e.g. if the source site is not
available), vSphere Replication uses the latest available data at the target site.
n
Rebuilds the replicated .vmdk files.
n
Reconfigures the newly replicated virtual machine with the correct disk paths.
n
Registers the virtual machine with vCenter Server at the target site.
You can recover one virtual machine at a time on the replicated site on the Incoming Replications tab.
Optionally, you can power on the recovered virtual machine. The recovered virtual machine's network
devices are disconnected. You might need to modify a recovered virtual machine to render it fully
operational.
This section includes the following topics:
n
Recover Virtual Machines by Using vSphere Replication
n
Failback of Virtual Machines in vSphere Replication
Recover Virtual Machines by Using vSphere Replication
With vSphere Replication you can recover successfully replicated virtual machines at the target site, one
at a time.
Prerequisites
Verify that the virtual machine at the source site is powered off.
Procedure
1 Log in to the vSphere Web Client for the target site.
2 On the Incoming Replications tab, right-click the virtual machine to recover and select Recover.
VMware, Inc.
68