In this post, I will use the Zerto Long Term Retention repository (LTR) I created in this post using the AWS Storage Gateway and S3 storage.
The first step is to create a VPG and target the AWS Storage Gateway as the LTR repository.
I create a new VPG from the Zerto dashboard.
Give the VPG a name:
Add some VMs to the
Follow the steps in
the wizard until you get to step 7: Retention Policy.
Slide the Long Term
Retention toggle to turn it on.
Since I configured
the AWS Storage Gateway already and set it as the default repository, it
automatically populates the target repository and connection information. Edit the retention information to meet your
needs and finish the wizard.
Once the replication via the AWS Storage Gateway to S3 completes, you’re ready to do a test restore. In the next post , I do a restoration from S3 via the AWS Storage Gateway.
While deploying the Zerto Cloud Appliance (ZCA) in Azure is straightforward, it does require that a Resource Group, networking, VPN and network security groups (NSGs) exist in Azure already.
In another blog post, I show you how to deploy the Zerto Cloud Appliance from the Azure Marketplace using an Azure Quickstart template. For you to be able to connect to the on-premises Zerto site, you will need a VPN in place.
In order to eliminate the separate VPN pre-requisite build step, we’ve now added a new Azure Quickstart template. This Quickstart template deploys the Resource Group, Network, NSGs, plus the VPN and the ZCA. How cool is that?
An Azure Subscription.
An account in Azure that has owner permissions to the subscription and the ability to add web apps in Azure.
An operational IPSec VPN endpoint on-premises
The pre-shared key for the VPN
The IP Address of the Local VPN Gateway
The IP subnet of the Local VPN in CIDR format
The IP Addressing for the private Azure network where the failed over VMs will run. A default of 10.3.0.0/16 is available, but this can be changed to your specific network scheme.
2. Click on the “Zerto Cloud Appliance with Site-to-Site VPN Connection” template in the gallery, and it takes you to the details page of the Quickstart template.
3. Click “Deploy to Azure”
4. This page provides a complete list of parameter definitions for the deployment in Azure.
5. Fill in Custom Deployment parameters page. Each setting has an information bubble that has a detailed explanation of what to enter in the field Many of the settings have default parameters filled in already.
6. Agree to the terms and conditions and click purchase.
7. The installation process takes about 30 minutes to deploy.
8. The deployment process is shown in the Azure portal.
Once the deployment completes, the message “Deployment succeeded” has a link to the resource group.
In the resource group, review all the Azure resources automatically created by the Quickstart template. If the VPN is online at the on-premises location, you should now have site-to-site connectivity. Try pinging from ZCA to ZVM, make sure your Windows firewall are properly configured for ICMP.