Zerto uses native Azure services to accelerate the move, failover and failover testing from on-premises to Azure. One of the ways Zerto achieves such short RTOs to public cloud is the use of Azure Scale Sets.
If you are not familiar with Azure Scale Sets, they are sets of VMs that power on automatically and perform a task and then deallocate automatically. Zerto uses them when a move, failover or failover test is performed.
In the following demo, you will see me initiate a failover from vSphere to Azure. Here’s what happens:
The scale set starts up 41 Linux worker VMs to process the replication data
I selected Reverse Replication in my Zerto failover. Once the VMs are running in Azure, the Scale Set works the delta sync from Azure to vSphere.
The Scale Set will process the Reverse Protection data until the Azure and vSphere sites are in sync.
Once the replication work is complete, the Scale Set will decommission all but one Scale Set VM that acts as the scheduler for the Scale Set.
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.