1. Keeping the Enterprise Always On with IT Resilience

2. Major disruptions are the norm, they are not rare events

3. Source: Forrester Disaster Recovery Journal 2013
1 in 3 companies has had at least one major disruption in the past 5 years

5. https://upload. wikimedia. org/wikipedia/commons/3/3c/Sp_apag%C3%A3o

8. We have to evolve beyond disaster recovery to IT Resilience

9. With IT Resilience you can withstand any disaster, confidently embrace change and Focus on Business

10. Business Impact of 1 Interruption
Example $100M Annual Revenue
Business Impact of 1 Interruption
RPO 24 Hours
Daily Backups
RTO 24 Hours
Impact $821,917
Storage Replication
RPO 4 Hours
RTO 4 Hours
Impact $136,986
Zerto Virtual Replication
RPO 20 Seconds
RTO 15 Minutes
Impact $2,980
Data Loss + Downtime + Data Entry
5pm
9am
[Script]
Here is an example of the pain and cost of your current solutions against your new solution with Zerto. To the left, we’re looking back in time to how much data we’re losing after a disaster, and to the right, we’re looking into the future and seeing the pain of recovering this data to the state it was in before the disaster.
[Click Auto Animation]
And if you look at the business impact of just 1 disaster, take a company with an annual revenue of $100M and consider the most basic calculation of data loss + downtime + data entry, we’re not even trying to include figures around brand impact, or the customer impact of an outage.
If you look at different technologies you might be using today, daily backups can give you a data loss of up to 24 hours, plus the 24+ hours it takes to recover the data.
Storage replication can reduce that impact but you are limited in how often you can take these snapshots and will still take you a few hours to recover that data at best.
With Zerto Virtual Replication, we’re going to take that recovery point to sub-twenty seconds, and recover it in 15 minutes or less. In terms of what that means with regards to data loss and downtime and reentry, it’s going to save you hundreds of thousands of dollars in the event of just one disaster and this actually makes Zerto free. It pays for itself is an immediate return of investment and allows you to prove to the business that you’ve invested in a technology that’s going to mitigate this risk.
[Click Animation]
And not only the risk of a power outage allowing you to recover to seconds before it happened, but also allows you to rewind and recover anything in minutes from any point-in-time direct to production or the recovery site, whether it’s the whole site, individual applications, virtual machines, or the files using Zerto.
So, if you have a Ransomware infection that occurred 2 hours ago, you don’t have to accept the data loss of going to the last backup. You can use Zerto/ZVR to rewind and recover to just seconds before that infection occurred, and this is a key benefit with Zerto.
[Click Slide Transition]
[Content Notes]
To update this data go to enter the customer revenue, current SLAs, Zerto SLAs and then update the figures in each row to match.
There is another version of this slide in the “optional slides” section, but simply showing the impact figures of a $10M annual revenue business instead of a $100M annual revenue business.
Minimize impact, re-wind and recover anything in minutes, from any point in time, direct to production or recovery site

11. DR IT Resilience Focused on downtime and disaster recovery
DR is a reactive response to catastrophic events.
Investments in recovery are seen as expensive insurance policies.
Downtime is measured in hours to days.
Lack of focus on everyday events that cause the majority of business disruptions
Poor planning, reporting, and metrics
IT Resilience
Focused on continuous availability
Limits downtime through preventive measures and rapid response
Investments driven by the need to serve customers and stay competitive.
Downtime is measured in minutes to hours.
Focused on all likely business disruptions
Emphasis on continuous improvement

12. Resilience for Evolving ITTM
Change 1 2
Protect 3
Consolidate
Key attributes of resilience 4
Transformation
Managed Service Providers 5
Simplify

13. TenCate: What does achieving Resilience look like?
Challenges
Growth Strategy through acquisition
Do you ever acquire a company with the same HW as you?
Cloud Strategy – how do we get there?
Ensuring applications and data are available
Solution: Resilience
Automated, Hypervisor-based Replication solution
No hardware or hypervisor dependencies
One solution across 20 sites in North America
Simplifies migrations:
300 GB ERP – CA to GA in 15 minutes
DR Plan 10 pages vs 300 pages
No more “Hit by the bus” Book
Recover applications in minutes with minimal data loss
Recover from ransomware with CDP
Deployed in AWS and Azure
Get to cloud simply and quickly
When you can achieve resilience, your IT Team is unstoppable.

14. Why is CDP important for resilience?
30 day Journal
06:00
09:00
18:00
00:00
12:00
15:00
Re-wind and recover from any point in time
Sites
VMs
Files
Apps

15. And when you aren’t resilient………it usually isn’t a secret.

19. Zerto - Right Technology, Right Time
4000 Customers Countries Clouds % Y/Y Growth
Proven Solution used by top global companies, at scale
Uber, Starbucks, Uber, CVS, Staples, McAfee, McKesson, MetLife & Kronos
“ the best damn platform ”
“ replicating constantly and having a RTO of 5 minutes or less ”
“ there’s a disaster, you have three buttons to worry about ”

20. Thank you

21. How Zerto Virtual Replication Works
No downtime, install in minutes Zerto Virtual Manager Management interface
Scale-out hypervisor-based Virtual Replication Appliance
Compression, throttling, resilience
Production Site
BC/DR Site
vCenter
vCenter
VM-Level Replication
[Required Slide]
[Background] There is a duplicate of this slide, with animations removed except for text boxes, in the optional section.
[Script]
How does this solution work?
[Click Animation]
The first thing you need to do is install the Zerto Virtual Manager (ZVM) that plugs into your vCenter or System Center depending on if you’re running VMware vSphere or Microsoft Hyper-V.
It’s a simple .NET (dot-net) installer that gives you an easy-to-use management interface along with the orchestration and automation capabilities.
ZVM installs in minutes with no disruption or down time.
The data is replicated using the scale-out, hypervisor-based Zerto Virtual Replication Appliance (VRA).
These are deployed from the Zerto Virtual Manager, they are very small in their footprint (1vCPU, 4GB (four gigabytes) of RAM, 12.5GB (twelve and a half gigabytes) of disk, and an IP address).
These are deployed on each and every hypervisor host that you are replicating from or to. This allows every protected VM to have a local replication appliance no matter where it moves around to within the cluster, and it creates this scale-out architecture meaning Zerto can protect your environment with the same software whether you are a 10-VM environment or have thousands of VMs to protect in your environment.
These appliances have built-in compression of the replication traffic and allow you to throttle it at different time periods throughout the day, and they also have resilience to WAN outages. So if a network link goes down they don’t start storing a huge amount of data, they just keep an online index in memory of the most recently changed blocks of data, which then replicate once the network link comes back online – it automatically self-heals.
[Click Auto Animation]
The VRAs are only replicating the virtual machine block-level changes.
It is performing real-time and continuous replication, removing the need for any scheduling. If nothing is changing, nothing is replicating, and as soon as a block changes and is written, it is asynchronously tracked and sent to the recovery site with no snapshots, and no impact.
ZVR is constantly tracking these writes and the order in which they are written as to capture recovery checkpoints that maintain this write-order fidelity of the data, without having to snapshot, pause, or stun the VM.
A great example here is Leupold & Stevens, a 5TB Oracle database before Zerto were using storage-based replication with snapshots which had to run every 4 hours with hot-backup mode impact, stunning the database and killing performance. With Zerto, they are now able to achieve and RPO of sub 20 seconds, no backup mode needed, no snapshots, no performance hit at all, and of course only seconds of data loss.
The recovery site contains virtual disks for the replica if the VM data, and journals for the latest changes, up to 30-days back.
With compressed data, typical DR site storage space required is the space for the utilized VM base disk, and an additional 7-10% of that space for the Journal.
Another great example here is Harpo Credit Union. They saved 40% of their storage footprint with Zerto. They no longer have to replicate the whole LUN, just the VMs, and they no longer need to take or store snapshots for point-in-time recovery.
[Click Slide Transition]
[Content Notes]
Scale-Out Example: Large SaaS provider. Scales to protecting thousands of VMs per vCenter, more than 10,000 VMs over 4 vCenters.
RPO Example; Leupold & Stevens, 5TB Oracle database, RPO of 4+ hours with hot-backup mode impact, to sub 20 seconds, no backup mode needed.
RPO Example vs Veeam: SQL Database for an online credit decision making company. They needed HA and VEEAM couldn't keep up, plus they were taking snapshots every 15 minutes which was pausing the application and creating latency. The SQL DBAs desired to use SQL always on and were trying to break Zerto Replication but couldn't. Finally the gave in and bought and now the whole company loves it!
Replica Data & Journal vDisk Example: HAPO Credit Union saved 40% of the storage footprint with Zerto. Not replicating LUNs, only VMs they needed & no snapshots.
Journal disk overhead sizing. This depends and varies with each customer and workload, but really it’s all about the data rate of change that is replicated and stored (not ongoing replication of disks selected as “swap”), and the amount of recovery history you wish to maintain for that VM. We do have a Journal sizing tool to help you get more accurate estimates. There are lots of safety measures built in to help prevent filling the storage and causing errors.
VM block-level changes only Near-sync Replication, RPO = Seconds Tracking & streaming, no snapshots, no impact
Storage-agnostic replicate any to any
Replica Data & Journaling vDisks
Any point in time recovery, 7-10%

22. One-To-Many Hybrid Cloud Architecture
Simultaneous local & multi-remote One-To-Many Replication, RPO = Seconds Pre-config networking, VPN, MPLS etc
Replica data in cloud storage, S3, blob ZCC, ZCA in AWS & Azure (Marketplace)
Cost effective, no recovery VMs until needed
Production Site
One-To-Many
[Required Slide]
[Background]
Introducing One-to-Many replication while also introducing all the supported destination types.
Use this slide to describe all the destination types. For a destination specific slide, see the optional slides.
[Script]
How does Zerto enable you to use the hybrid cloud?
[Click Animation]
We do this with One-to-Many replication which allows us to simultaneously replicate a VM to multiple destinations.
You can replicate to multiple sites including local and remote sites, while still maintaining that Recovery Point Objective (RPO) of just seconds.
Preconfigure the networking to link the source site to the various destination sites, and this is how you can replicate to another site!
Then we can replicate to hybrid cloud remote sites including Azure and AWS sites, or a Zerto Cloud Service Provider, and you will just store the replica data at the destination site and not the destination VMs. You aren’t paying for the recovery VMs until you want to failover and recover those VMs, or run a failover test for a short period of time.
In the public cloud you have a Zerto Cloud Appliance that does two things. (1) It allows management for you to click-to-failover in the cloud, and (2) to accept and manage the replica data. So you just have this management VM, and the data is in the cheap cloud storage until you need to click to failover.
If you’re doing local replication, using One-to-Many, this allows you to recover anything into production within minutes. You can recover individual files or objects within the VM, recover a single VM or multi-VM VPG, or even apply local protection between storage arrays.
This let’s you maintain multiple SLAs for the same VMs. Maybe you want to take advantage of cheaper cloud storage and utilize a longer Journal retention there, which maintaining a shorter Journal locally. Or vice-versa in the event you want to maintain a longer 30-day Journal locally to maintain file-level recovery speed and replace your current backup solution for end-user file restore requests. You can keep a much shorter Journal in the cloud if you prefer to only failover the entire site at once when using the cloud site, for example.
The point is, you can mix and match depending on what will works best for your organization and environment. Use the cloud to drive efficiencies while minimizing impact.
[Click Slide Transition]
[Content Notes]
Azure: ZCA is D3 V2 VM deployed from market place. Needs existing VPN gateway or Express Route to Virtual Network. Pre-configure VM Virtual Network, Subnet, Instance family, instance size, Network Security Group and assign a Private IP in VPG settings. Max VM disks >1TB due to page blobs limit. Journal as block blobs. Storage account auto created on install. Recovered VMs created in new Resource Group (ARM, Azure Resource Manager, not classic). VMs directly mounted from storage account. RTO therefore <5 minutes.
AWS ZCA is M4.xLarge instance manually deployed. Needs existing VPN to VPC or Direct Connect. Pre-configure VPC Network, Subnet, Security Group, Instance size & Static IP in VPG settings. Max 1TB disks. Data in S3 bucket auto created on install. Recovered VMs created using EC2 import API, RTO dependent on size of disks. Typically 1-4 hours.
ZCSP: ZCC is deployed and managed by cloud provider. Simple VM with 2 NICS, 1 customer facing as replication target. Needs existing VPN or MPLS. Pre-configure networking & IPs in VPG settings. No conversion of VM needed as CSP is native VMware delivering RTO <5 minutes.
*Note: One-To-Many requires ECE licensing, covered later in deck.
Hybrid Example: IAG (Insurance Australia Group) 1k+ VMs, bought Zerto not only for the RPOs in seconds, RTOs in minutes and reduced business impact, but for the future proofing their infrastructure to replicate to any target cloud in the future
Recover VMs, files & folders Restore Anything To Production In Minutes Protect between local storage
Multi-SLA journal retention
On-Premises & Hybrid Cloud DR
All-in-one solution, drive cloud efficiency

23. Consistent Protection & Recovery
Production Site
LUN Consistency Group evolved = Virtual Protection Group
Simple, scalable, protection & recovery of VMs, not LUNs
Enterprise Applications
Protect all VMs & recover multi-VM application stacks together
CRM, ERP, SQL, Oracle, SharePoint, Exchange
Point in time recovery, write ordering & consistency
Pre-configure recovery settings, network etc, prioritize VPGs
Support virtualization features vMotion, svMotion, HA etc
RPO 4 seconds
VPG1
[Required Slide]
[Background] Introducing the concept of ZVR’s Virtual Protection Groups (VPG), including calling out some supported features and functionality.
[Script]
One key concept in Zerto is Consistency Grouping. We took the concept of placing all the VMs on the same storage LUN in order to achieve data consistency between replicated VMs on that storage, and applied across all storage in your environment. Typically, you would take all the VMs that belong to your enterprise application and place them on the same LUN, snapshot that LUN, replicate it and recover the LUN, and all your VMs will be there from the same point-in-time.
What if you want to mix and match storage or LUNs for your VMs, but still want to maintain data consistency between them? What if you want to replicate to the cloud? You can’t do that with traditional methods using storage replication across multiple arrays or vendors.
Zerto took the replication and moved it into the hypervisor so it’s no longer dependent on the storage replication.
[Click Animation]
With our Virtual Protection Groups, we protect all the VMs together that you add to this VPG, give them all granular checkpoints with write-order-fildelity across the VMs, and allow you to recover them together from the same point-in-time.
It doesn’t matter what storage or LUN there on; replicate from anything to anything.
When you create the protection group, you preconfigure all your settings -- networks, security, sizing, prioritization, etc -- so it’s all ready to go when you need to failover.
[Click Slide Transition]
[Content Notes]
RPO 6 seconds
VPG2
RPO 9 seconds
VPG3

24. Remove Reliance On Individuals
Disaster Event!
Recovery Process:
Click Failover 1
Select Apps 2
[Required Slide]
[Background] The recovery process walkthrough messaging the removal of reliance on individuals.
[Script]
Another key thing with Zerto is we’ve remove the reliance on individuals. If you had a disaster today, how many people would you have to get together and how much would you have to do to orchestrate all of this no matter what time of day (or night)? Prior to using Zerto, no matter the size of the environment you have, you are calling your most skilled employees in each area in order to help you through this process to ensure success. Hope the knowledgeable resources are still on-board or have transitioned their (tribal) knowledge for the process.
With Zerto, it’s four simple steps!
[Click Animation]
1.) You click Failover
2.) Select your applications (VPGs). It could be just one, all, or a subset of all of them.
3.) Verify your recovery settings and decide if you want to recover to the most recent checkpoint, or a validated checkpoint further back in the past. It’s just a checkbox.
4.) Click the Failover button and let Zerto do the rest. It really is as simple as that.
That is all your DR plan needs to contain in order to perform the failover.
[Click Slide Transition]
[Content Notes]
Verify 3
Start Failover 4

25. DRaaS to Microsoft Azure
Management of scale-out architecture Zerto Virtual Manager (ZVM) & VRAs
Configure networking to Azure separately
D3 V2 Azure Windows VM
All in One Zerto Cloud Appliance
Manage & invoke DR from Azure
Production Site
Azure
vCenter
ZVM
ZCA
VPN Gateway VM
VRA VM
VRA VM VM VM VM
VM-Level Replication
Consistency groupings, point in time recovery Async, Block-level replication, RPO = Seconds Pre-configure Azure recovery settings
No recovery VMs until needed RTO = Minutes, Automated VM import
Replica data in Storage Account

26. Re-wind and recover from any point in time
Extended Journal
30 day Journal
06:00
09:00
18:00
00:00
12:00
15:00
Re-wind and recover from any point in time
Sites
VMs
Files
Apps

27. Zerto Mobile SaaS Delivered No VPN
Single view across multiple ZVMs & sites
Take Zerto Anywhere
Securely stored, managed, accessed
Starting with monitoring only
Show during Mobile demo video
Marie - Replace screen on phone with new one

28. Resilience for Evolving ITTM
Resilience for Evolving IT
Public Cloud Storage/IaaS
Zerto
Cloud Continuity Platform
Next Gen Apps PaaS
Enterprise IT
MSP
Oded – Also looking at:
KVM & Openstack
SaaS protection
Containers & Docker
On Premise Production
SaaS 28

29. Q&A