Prerequisites and Considerations for Site Recovery Manager for Google Cloud VMware Engine
Site Recovery Manager on Google Cloud VMware Engine uses vSphere replication which solutions needs to be installed Configured and managed by the customer. In order to perform these actions, we need to validate the pre-requisites and plan at each steps.
Before installing Site Recovery manager on the Google Cloud VMware Engine, you must be aware of and complete the following prerequisites:
- Create a private cloud in the VMware Engine portal
- Check SRM version compatibility with vSphere on the for both the primary and recovery Site.
- Check the vCenter version of primary and recovery site
- VMware Customer Connect account to download the SRM management and replication appliances.
- Decide the topology for deployment (private cloud is primary or replication site).
- A valid license for SRM.
- Verify that your identified on-premises configuration is within the supported limits in the documentation page
- Sufficient network bandwidth to meet your workload size and Recovery Point Objective(RPO) requirements. For more information, see .
Preparing for Deployment
After you have completed the prerequisites, you must complete the following steps in preparation for deployment:
- Create a new dedicated SRM network using one of the built-in Service Subnets found in the VMware Engine networking portal. Best practice is to use service subnets instead of NSX overlay networks due to the reduction in networking overhead.
- Setup connectivity between the On-prem and cloud (assuming your primary site is on-prem and GCVE private cloud is acting as recovery Site). You must use a site-to-site VPN or Cloud Interconnect. For more information, see the and the Google Cloud .
- Setup infrastructure services such as AD, DNS and DHCP
- Active Directory (AD). Identify users from your on-premises AD in your private cloud. Set up an AD in your private cloud for all users.
- DNS and DHCP services. To provide IP address lookup, IP address management, and name resolution services for your workloads in the private cloud, set up a DHCP and DNS server as described in .
- DNS forwarding. The
gcve.googdomain is used by management VMs and hosts in your private cloud. To resolve requests to this domain, configure DNS forwarding on the DNS server as described in . This also lets you use fully qualified domain names (FQDNs) instead of IP addresses during the vSphere Replication appliance and SRM installation.
- Prepare a solution user account for installation.
- You must install the vSphere Replication appliance and SRM using a user with administrator privileges in the vCenter SSO domain. This helps ensure high uptime and availability for your private cloud vCenter environment.
- For the installation process, use one of the available in your private cloud.
- Configure firewall rules for the vSphere Replication appliance. For a list of port numbers that must be open for vSphere Replication, see
- Plan your Workload security which can involve but not limited firewall, routes, access restrictions etc for the period when the disaster recovery site is running the production workload. VMware NSX is a great product which can helps define these security configurations.
Deployment and Configuration Considerations
- Validate that the name records for replication and management appliance is resolvable on both sites.
- Install vSphere replication appliance on both sites and configure the same. Refer to documentation for the detailed procedure.
- Install Site Recovery Manager on your private cloud. The procedure is the same as the procedure for the on-premises installation. See .
- Install the Site Recovery Manager License Key. See .