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
Replicating Virtual Machines 8
With vSphere Replication you can replicate virtual machines from a source site to a target site.
You can set a recovery point objective (RPO) to a certain time interval depending on your data protection
needs. vSphere Replication applies all changes made to virtual machines configured for replication at the
source site to their replicas at the target site. This process reoccurs at the RPO interval that you set.
To replicate a virtual machine using vSphere Replication, you must deploy the vSphere Replication
appliance at the source and target sites. A vSphere Replication infrastructure requires one
vSphere Replication appliance at each site.
The source and target sites must be connected for you to be able to configure replications. If one of the
sites is unreachable from the other site, is offline, if authentication fails, or if the certificates have changed,
it shows the disconnected state in the vSphere Replication interface. You cannot perform replications if
one of the sites is in the disconnected state due to these reasons. The sites can also appear in the
disconnected state if you log in to the vSphere Web Client when a previous login session has expired.
In this case, scheduled replications continue as normal. See vSphere Replication Sites Appear in the
Disconnected State.
vSphere Replication does not support the recovery of multiple virtual machines from the same workflow.
Each recovery workflow is for an individual virtual machine.
You cannot replicate powered-off virtual machines. Replication begins when the virtual machine is
powered on. You cannot use vSphere Replication to replicate virtual machine templates.
This section includes the following topics:
n
How the Recovery Point Objective Affects Replication Scheduling
n
Replicating a Virtual Machine and Enabling Multiple Point in Time Instances
n
Using vSphere Replication with Virtual SAN Storage
n
Replicating Virtual Machines Using Replication Seeds
n
Replicating a Virtual Machine in a Single vCenter Server Instance
n
Configure Replication for a Single Virtual Machine
n
Configure Replication for Multiple Virtual Machines
n
Move a Virtual Machine to a New vSphere Replication Server
VMware, Inc.
56