Before you implement disaster recovery in VMware Cloud Foundation, your environment must support certain prerequisites for deployment and networking.
You implement disaster recovery for vRealize Automation,vRealize Suite Lifecycle Manager, and vRealize Operations Manager. The disaster recovery scenario of the Cloud Management and the Operations Management platforms are validated and require the following prerequisites.
Disaster Recovery Considerations
When you prepare for disaster recovery, you must determine which of your two Cloud Foundation instances will function as the protected site and which one as the recovery site.
The protected site hosts the business-critical SDDC services. In the context of Cloud Foundation, the protected site contains the vRealize products, including vRealize Operations Manager, vRealize Suite Lifecycle Manager and vRealize Automation, with failover that is enabled in the event of a disaster.
The recovery site is an alternative location to which these vRealize applications are migrated and hosted in the event of a disaster.
In this guide, the protected site is referred to as Region A and the recovery site is referred to as Region B.
Disaster Recovery Prerequisites
Before you implement disaster recovery, verify that your environment satisfies the following prerequisites:
Download the VMware Site Recovery Manager 8.2 .iso image and mount it on the machine that you use to access the vSphere Client. In each region, provide the environment configuration for Site Recovery Manager deployment.
Attribute Protected site Recovery Site Cluster sfo01-m01-mgmt01 lax01-m01-mgmt01 Datastore sfo01-m01-vsan01 lax01-m01-vsan01 Number of CPUs 2 2 Memory (GB) 8 8 Disk space (GB) 20 20 Virtual machine network sfo01-m01-vds01-management lax01-m01-vds01-management
- Download the vSphere Replication 8.2 .iso image and mount it on the machine that you use to access the vSphere Web Client. In each region, provide the environment configuration for deploying the vSphere Replication virtual appliance.
Attribute Protected site Recovery Site Cluster sfo01-m01-mgmt01 lax01-m01-mgmt01 Datastore sfo01-m01-vsan01 lax01-m01-vsan01 Number of CPUs 4 4 Memory (GB) 8 8 Disk space (GB) 26 26 Virtual machine network sfo01-m01-vds01-management lax01-m01-vds01-management
- Obtain a license for Site Recovery Manager.
Cloud Foundation Prerequisites
- Verify that VMware Cloud Foundation is version 3.9.1.
- Verify that you have obtained a Cloud Foundation license that covers the use of cross-vCenter NSX objects.
- Deploy vRealize Suite Lifecycle Manager, vRealize Automation, and vRealize Operations Manager in Region A after you deploy or upgrade VMware Cloud Foundation to 3.9.1.
- Temporarily migrate all virtual machines on NSX logical switches to VLAN-backed distributed port groups to keep their connectivity and disconnect the virtual machines from the logical switches. You can reconnect these virtual machines to the logical switches after NSX is configured for cross vCenter Server operations.
- The regions must be connected to each other and the connection must support jumbo frames and Layer 3 routing between the regions.
- All uplinks, port channels, and VLANs that carry VXLAN and vSphere Replication traffic must be configured for jumbo frames.
- The maximum supported latency between regions must be 150 ms.
- Sufficient bandwidth must be available for replication traffic. See vSphere Replication Calculator at http://www.vmware.com/vrcalculator for the initial guidance.
- BGP must be licensed and available for use on the Layer 3 devices in both regions.
- If you upgrade Cloud Foundation to 3.9.1 and do not have application virtual networks configured, contact VMware Support for additional guidance on configuration and migration of application virtual networks, before performing distaster recovery or planned migration.
- Nexus switches must be updated to a Nexus OS release that supports routing protocol adjacencies over virtual port channels. See https://www.cisco.com/c/en/us/support/docs/ip/ip-routing/118997-technote-nexus-00.html for the minimum required Nexus OS release and additional configuration required.