Configuring disaster recovery using Zerto
To provide business continuity in the event of a disaster, you can set up your Google Cloud VMware Engine private cloud as a recovery site for your on-premises applications. You can follow a similar approach to set up the private cloud as a primary site that is protected by a recovery site on-premises, at a different location, or in a different VMware Engine private cloud.
The replication and orchestration platform for the recovery solution described in this document is based on Zerto 8.5 and later. This recovery solution allows critical infrastructure and application virtual machines (VMs) to be replicated continuously from your on-premises vCenter to your private cloud.
This recovery solution offers the following benefits:
- Eliminates the need to set up a data center specifically for disaster recovery.
- Helps with worldwide geographic resilience by leveraging the Google Cloud locations where VMware Engine is deployed.
- Gives you an option to reduce deployment costs and total cost of ownership for disaster recovery.
This recovery solution requires you to do the following:
- Install, configure, and manage Zerto in your private cloud.
- Provide your own licenses for Zerto when the private cloud is the protected site. You can pair Zerto running on the site with your on-premises site licensing.
Zerto disaster recovery architecture
Before you begin
To enable Zerto Virtual Replication from your on-premises environment to your private cloud, complete the following prerequisites:
- Connect your on-premises network to your VMware Engine private cloud
- Set up DNS lookup of your private cloud management components from your on-premises network to
forward requests to your private cloud DNS servers.
To enable forwarding of DNS lookup, create a forwarding zone entry in your
on-premises DNS server for
gve.googto private cloud DNS servers.
- Set up DNS lookup for on-premises vCenter components to be forwarded to your on-premises DNS servers. The DNS servers must be reachable from your private cloud.
- Install a Microsoft Windows server on your private cloud.
- Install Zerto Virtual Manager (ZVM) on the Windows server.
- Identify a solution user account to use with ZVM, and set a strong password for the solution user account.
Optional configuration on your private cloud
- Create one or more resource pools on your private cloud vCenter to use as target resource pools for VMs from your on-premises environment.
- Create one or more folders on your private cloud vCenter to use as target folders for VMs from your on-premises environment.
- Create subnets on your private cloud for your failover network and set up required firewall rules.
- Install or configure DHCP and DNS servers or use an Active Directory domain controller in your private cloud.
Deploy a disaster recovery solution using Zerto in your private cloud
The following sections describe how to deploy a disaster recovery solution using Zerto Virtual Replication in your private cloud.
Set up ZVM and VRA on your private cloud
- Install Zerto Virtual Manager (ZVM) on a Windows server in your private cloud.
- Sign in to Zerto Virtual Manager using a solution user account from your private cloud.
- Set up licensing for Zerto Virtual Manager.
- Install Zerto Virtual Replication Appliance (VRA) on the ESXi hosts of your private cloud.
- Pair your private cloud ZVM with your on-premises ZVM.
Set up a Zerto virtual protection group
- Create a virtual protection group and specify its priority.
- Select the VM that require protection for business continuity and customize the boot order, if needed.
Select the recovery site as your private cloud and the default recovery server as the private cloud cluster or the resource group you created. Select vsanDatastore for the recovery datastore on your private cloud.
Customize storage options as required.
Specify the recovery networks to use for failover network and failover test network, providing the subnets created earlier, and customize the recovery scripts, as required.
Customize the network settings for individual VMs, if necessary, and create the virtual protection group.
After the replication completes, test your failover.