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
Network Based Storage
Network bandwidth requirements increase if all storage is network-based because data operations
between the host and the storage also use network. When you plan your deployment, be aware of the
following levels of traffic:
n
Between the host running the replicated virtual machine and the vSphere Replication server.
n
Between the vSphere Replication server and a host with access to the replication target datastore.
n
Between the host and storage.
n
Between storage and the host during redo log snapshots.
Network based storage is a concern when you are replicating virtual machines within a single vCenter
Server instance that shares the network for the levels of traffic listed. When you have two sites with a
vCenter Server instance on each site, the link speed between the two sites is the most important as it can
slow down replication traffic between the two sites.
Dataset Size
vSphere Replication might not replicate every virtual machine nor every VMDK file in the replicated virtual
machines. To evaluate the dataset size that vSphere Replication replicates, calculate the percentage of
the total storage used for virtual machines, then calculate the number of VMDKs within that subset that
you have configured for replication.
For example, you might have 2TB of virtual machines on the datastores and usevSphere Replication to
replicate half of these virtual machines. You might only replicate a subset of the VMDKs and assuming all
the VMDKs are replicated, the maximum amount of data for replication is 1TB.
Data Change Rate and Recovery Point Objective
The data change rate is affected by the recovery point objective (RPO). To estimate the size of the data
transfer for each replication, you must evaluate how many blocks change in a given RPO for a virtual
machine. The data change rate within the RPO period provides the total number of blocks that
vSphere Replication transfers. This number might vary throughout the day, which alters the traffic that
vSphere Replication generates at different times.
vSphere Replication transfers blocks based on the RPO schedule. If you set an RPO of one hour,
vSphere Replication transfers any block that has changed in that hour to meet that RPO.
vSphere Replication only transfers the block once in its current state at the moment that
vSphere Replication creates the bundle of blocks for transfer. vSphere Replication only registers that the
block has changed within the RPO period, not how many times it changed. The average daily data
change rate provides an estimation of how much data vSphere Replication transfers or how often the
transfers occur.
VMware vSphere Replication Administration
VMware, Inc. 24