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.

Zerto Solution version 9.5u1 and later are supported with VMware Engine. 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 Solution in your private cloud.
  • Provide your own licenses for Zerto Solution 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

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:

  1. Connect your on-premises network to your VMware Engine private cloud
  2. 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 to private cloud DNS servers.
  3. 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.
  4. Install a Microsoft Windows server on your private cloud.
  5. Install Zerto Virtual Manager (ZVM) on the Windows server.
  6. 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

  1. Create one or more resource pools on your private cloud vCenter to use as target resource pools for VMs from your on-premises environment.
  2. Create one or more folders on your private cloud vCenter to use as target folders for VMs from your on-premises environment.
  3. Create subnets on your private cloud for your failover network and set up required firewall rules.
  4. 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

Follow the Zerto documentation for deploying the Zerto Virtual Replication solution on your private cloud. The private cloud can be a protected site or a recovery site of your Zerto Solution.

Set up workload automation on Zerto Virtual Manager of your private cloud

The following sections describe the required and optional workload automation settings on Zerto Virtual Manager of your private cloud. These settings must be enabled to ensure Zerto Virtual Replication Appliance is gracefully managed during the node addition and host maintenance of nodes of your private cloud.

  1. In the Zerto Virtual Replication interface, under Site Settings, select Workload Automation.
  2. Select Enable VRA auto evacuation once entering maintenance mode option in Host Maintenance Mode section. This option is required to gracefully evacuate VRA during a failed node replacement, private cloud node removal and upgrades or patching of your private cloud.
  3. Optionally select : Enable VRA auto installation once host is added to cluster option in VRA Deployment section. Enabling this option allows Zerto Virtual Replication to deploy a Zerto Virtual Replication Appliance when you expand your private cloud cluster.

What's next