5.8
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 to vCenter Server
- Configure Replication for Multiple Virtual Machines to vCenter Server
- Move a Virtual Machine 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 Target Datastore Location
- Change the Point in Time Settings of a Replication
- 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 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
- 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
- Error at Reconfiguring the vSphere Replication Management Server from the Virtual Appliance Management Interface
n
Stop Replicating a Virtual Machine
n
Reconfiguring Replications
How the Recovery Point Objective Aects Replication
Scheduling
When you set a Recovery Point Objective (RPO) value during replication configuration, you determine the
maximum data loss that you can tolerate. The RPO value affects replication scheduling, but
vSphere Replication does not adhere to a strict replication schedule.
For example, when you set the RPO to 15 minutes, you instruct vSphere Replication that you can tolerate
losing the data for up to 15 minutes. This does not mean that data is replicated every 15 minutes.
If you set an RPO of x minutes, the latest available replication instance can never reflect a state that is
older than x minutes. A replication instance reflects the state of a virtual machine at the time the
replication starts.
Assume that during replication configuration you set the RPO to 15 minutes. If the replication starts at
12:00 and it takes five minutes to transfer to the target site, the instance becomes available on the target
site at 12:05, but it reflects the state of the virtual machine at 12:00. The next replication can start no later
than 12:10. This replication instance is then available at 12:15 when the first replication instance that
started at 12:00 expires.
If you set the RPO to 15 minutes and the replication takes 7.5 minutes to transfer an instance,
vSphere Replication transfers an instance all the time. If the replication takes more than 7.5 minutes, the
replication encounters periodic RPO violations. For example, if the replication starts at 12:00 and takes 10
minutes to transfer an instance, the replication finishes at 12:10. You can start another replication
immediately, but it finishes at 12:20. During the time interval 12:15-12:20, an RPO violation occurs
because the latest available instance started at 12:00 and is too old.
The replication scheduler tries to satisfy these constraints by overlapping replications to optimize
bandwidth use and might start replications for some virtual machines earlier than expected.
To determine the replication transfer time, the replication scheduler uses the duration of the last few
instances to estimate the next one.
Replicating a Virtual Machine and Enabling Multiple Point
in Time Instances
You can recover virtual machines at specific points in time (PIT) such as the last known consistent state.
When you configure replication of a virtual machine, you can enable multiple point in time (PIT) instances
in the recovery settings in the Configure Replication wizard. vSphere Replication retains a number of
snapshot instances of the virtual machine on the target site based on the retention policy that you specify.
vSphere Replication supports maximum of 24 snapshot instances. After you recover a virtual machine,
you can revert it to a specific snapshot.
VMware vSphere Replication Administration
VMware, Inc. 53