Zerto Goes Public, and Back! Etti Chechik Leibovitch Tamir Solomon

Size: px
Start display at page:

Download "Zerto Goes Public, and Back! Etti Chechik Leibovitch Tamir Solomon"

Transcription

1 1

2 Zerto Goes Public, and Back! Etti Chechik Leibovitch Tamir Solomon 2

3 Azure Platform By Etti Chechik Leibovitch AWS Platform By Tamir Solomon 3

4 4 I believe that my organization will eventually run some of the mission critical applications in the public cloud

5 We re running mission critical applications in the public cloud TODAY 5

6 6 Which One?

7 7 A World of Uninterrupted Technology for Business and People

8 Public Cloud as DR site Global On-demand resources DIY Limit infrastructure expenses No maintenance No out-of-life products Elasticity Accessibility 8

9 What s new with Azure Etti Chechik Leibovitch 9

10 Zerto Goes Public and Back! ZVR 5.0 Coming soon 10

11 Zerto Virtual Manager (ZVM) & VRAs Configure networking to Azure separately Replication to Azure All-in-One Zerto Cloud Appliance Zerto appliance available in Azure Marketplace On-Premises Azure Region - Subscription vcenter VPN Gateway ZCA ZVM VRA VM-Level Replication Zerto Standard Storage Account Journal Recovery 11

12 Recovery in Azure Automated Failback! On-Premises VM Recovery, RTO = Minutes Re-IP, Scripts Azure Region - Subscription vcenter VPN Gateway ZCA ZVM VRA VM-Level Replication Zerto Standard Storage Account Journal Recovery vhd vhd 12

13 Global organizations Protect your critical applications wherever they are with Azure as DR site Failover Failback to-premises Clone Test Recover Files from Journal Move BC/DR Use Cases To Azure 13

14 BC/DR Use Cases To Azure Meet compliance requirements One to Many some/all copies in Azure VM Keep longer history in Azure VPG1 to VC 24 hours VPG2 to Azure 1 month 14

15 Migration Use Cases To Azure Entire on-premises datacenter to Azure Some of the workload on-premises to Azure DR datacenter migration to Azure 15

16 Always-on Replication to Azure RPO = Seconds RTO = Minutes 30 day Journal No cost for recovery VMs until failover 16

17 Always-on Replication to Azure One-to-Many File Level Restore from Journal More.. 17

18 Failback to On-Premise using Move RTO = Minutes On-Premises Always on replication Configure networking to on-premise Azure Region - Subscription vcenter VPN Gateway ZCA ZVM VRA VMDK VM-Level Replication Zerto Standard Storage Account VMDK Journal Recovery 18

19 Replication out of Azure for failback, protection and recovery of production workloads 19

20 Protection of Azure Virtual Machines Protection of Recovered workload Protection of workload that meet these Criteria: VMs in ZCA s region and subscription All disks reside on Zerto Storage Account 20

21 BC/DR and Migration Use Cases From Azure Protect Azure VMs* to your own private datacenter Migrate Azure VMs* to your own private datacenter. Failover Test Clone Recover files from Journal Move * VMs on Standard Storage Account. Recovery and Test require protected VMs to be stopped 21

22 BC/DR Services DR services? Be Better, Go Global Onboarding customers - easy and fast Go Global! DR services anywhere Burst into the cloud get prepared for D(R)-Day! Strict compliance requirements? Multiple remote copies some/all in Azure Local and remote copy We want to hear more! 22

23 What To Expect When DR ing To Azure? RPO = Seconds RTO = Minutes ZCA and Zerto storage account coupling Use MOVE to failback to on-premise Test first! 23

24 What s Next? Future Items Considered Mutli-Storage Account Support Premium-Storage Account Support VISIT US at the Demo Booth! More.. 24

25 Your Top 3 Takeaways 1. Failback from Azure is the primary use case in the upcoming version 2. Protection of Azure VMs is doable but has limitations 3. Yet another ZVR release that supports the vision 25

26 Zerto Goes Public, and BACK! with the AWS Platform Tamir Solomon Product Owner 26

27 4.x-5.0 Zerto AWS Overview AWS support since version 4.0 Higher RTOs than other hypervisors and Azure Disks saved as S3 objects. Imported to EBS and EC2 upon Failover Official AWS APIs are used Bound by Limitations (e.g. 1TB) 27

28 Introducing the new Importer Proprietary import mechanism Up to 9x faster RTO AWS Import limitations - No longer relevant Temp. AWS Instances per Volume (Zerto Importer) Scale out architecture 2:49:06 0:25:41 Win GB OS disk 256 GB data disk 28 Before After

29 3 Alternatives. What Should I Use? zimport for data volumes Faster recovery times Data disks > 1TB zimport for all volumes Fastest Recovery times Requires drivers on the protected VMs AWS Import No reason, really. 29

30 What To Expect When DR ing To AWS Q: What is the additional cost Impact? Assuming 50GB OS + 500GB data volume using an m4.xl instance at ~100MBps - $0.25 per failover Q: Do I need to install drivers on the protected VM? Only if zimport for all volumes was selected Q: How can I get these drivers? On for Windows Additional details in Zerto s documentation 30

31 What To Expect When DR ing To AWS Q: Can I change the zimporter size? Not at this point, this is planned for next release Q: Does it support different EBS disk types? Not at this point, this is planned for next release Q: Does it pose a security concern? Even though zimporters are created with public IP, they are connected to the ZCA subnet and security groups. Additionally, we are creating a dedicated security group with external access only. 31

32 Things We Are Considering Next Configurable zimport instance sizes Configurable recovery EBS disk type Multi-AZ support Come to visit our booth VISIT US at the Demo Booth! 32

33 33 goes public and BACK???

34 Thank You! Etti Chechik Leibovitch Tamir Solomon 34