We are now in the seventh section of the blueprint ,In this section we are going to cover “Deploy and manage vSphere Replication”
Here are the objective from the blueprint :
- Configure and manage a vSphere Replication infrastructure:
- Isolate vSphere Replication network traffic
- Enable data compression of vSphere Replication traffic
- Configure and manage vSphere Replication of virtual machines
- Analyze and resolve vSphere Replication issues:
- Storage configuration
- Multiple point in time snapshots
- Enabling vSphere Replication on VMs
- 2 Datacenter
- VMware vSphere Replication Administration
Configure and manage a vSphere Replication infrastructure and Configure and manage vSphere Replication of virtual machines:
Configuration and management:
Isolate vSphere Replication network traffic:
You isolate the network traffic to the vSphere Replication Server by dedicating a VMKernel NIC on each ESXi host on the primary site that sends data to the vSphere Replication Server.By default, the vSphere Replication appliance has one VM network adapter that is used for various traffic types:
- Management traffic.
- Replication traffic.
- Traffic between vCenter Server and vSphere Replication Management Server. (You can add network adapters to the vSphere Replication appliance and use the VAMI to configure a separate IP address to use for each traffic type).
Because the default VM network adapter is used for different types of traffic, you can add network adapters to the appliance, and configure vSphere Replication to use a separate adapter for each traffic type.
- In the Appliance edit Settings add additional NIC’s
- In the appliance GUI configure the new NIC’s
Enable data compression of vSphere Replication traffic:
You can configure vSphere Replication to compress the data that it transfers through the network.
Analyze and resolve vSphere Replication issues:
- The target site must have hardware, network, and storage resources that can support the same virtual machines and workloads as the source site.
- VM with multiple disks in multiple datastore – error msg: “Multiple source disks with device keys device_keys point to the same destination datastore and file path disk_path.”
- Solution : On the target site select different datastore for target VMDK files.
- The Replication Pauses When You Add a New Disk To the Source VM
- Solution: Include / Exclude the the new disk in the replication
- Shared Disk Support – vSphere Replication cannot replicate virtual machines that share vmdk files in this release.
- Raw Device Mapping (RDM) – vSphere Replication supports replicating RDMs in Virtual Compatibility Mode. RDMs in Physical Compatibility Mode cannot be configured for replication.
- Snapshots – vSphere Replication does not replicate virtual machine snapshot hierarchy at the target site.
Multiple point in time snapshots:
vSphere Replication can save replication instances that can be used as snapshots after recovery or planned migration operations. You can save up to 24 point in time instances per VM. If you selected to disable the saving of point in time instances, the instances that exist on the target site are deleted when the next replication instance appears on the target site. The moment when a new replication instance is saved on the target site depends on the RPO setting.
Enabling vSphere Replication on VMs:
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. in such cases you will get an error because the virtual machine name must be unique in the same folder.
- The error msg : Unable to register the recovered virtual machine VM_name with configuration file <path_to_vmx_config_file>.
- The solution: Recover the virtual machine in a different VMs and Templates folder in the same datacenter.
Thanks for reading