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 a Virtual Machine in a Single vCenter Server
Instance
You can use vSphere Replication to replicate a virtual machine in a single vCenter Server even if the
vCenter Server instance has only one host in its inventory.
When you configure replication in a single vCenter Server instance, you can select the source site as the
target site for replication. You then configure replication in the same way as for an infrastructure with a
source and a target site. For example, you can replicate a virtual machine to a different datastore
attached to the same host or another host. vSphere Replication prevents you from using the source or
replicated virtual machine's vmdk files as the target of the replication.
The virtual machine name must be unique in the same folder in the vCenter Server inventory. In the
recovery wizard, vSphere Replication does not allow you to select a folder if there is already a virtual
machine with the same name registered to it. During recovery if there is a virtual machine with the same
name, you might see an error message. See Error Recovering Virtual Machine in a Single vCenter Server
Instance for more information.
Note If you install vSphere Replication as part of a vCenter Site Recovery Manager (SRM) deployment,
any replications that you configure in the same vCenter Server instance are not visible in the SRM user
interface. You can still monitor and manage these replications in the vSphere Replication user interface in
the vSphere Web Client.
Configure Replication for a Single Virtual Machine
vSphere Replication can protect individual virtual machines and their virtual disks by replicating them to
another location.
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 no
more than 1 hour of data during the recovery. For smaller RPOs, 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.5 for Microsoft Volume Shadow Copy Service (VSS) quiescing support for Windows virtual
machines.
VMware vSphere Replication Administration
VMware, Inc. 61