Zerto Virtual Replication 5.0

Zerto Virtual Replication 5.0
BC/DR Technology for the Enterprise Cloud R M Sugiarto Wisepac Mobile Instructions for Presentation Notes This presentation is utilized as a starting point to introduce new and prospective customers to Zerto and Zerto Virtual Replication. Remember, when we speak of any features and functionality messaging with Zerto Virtual Replication (ZVR), we are speaking and referring to ZVR ECE (Enterprise Cloud Edition). We always start there and work our way back when and if necessary for a particular audience or question. NOTES: As always, adjust this presentation as necessary for your particular target audience. There are many slides at the end which are hidden in the “optional slides” section. Use these as necessary. If you find you have changed and prefer the slide ordering a certain way, please let us know so we can update and share this with everyone to take advantage of. If you need a slide created or updated to tell a different/better story, please let us know and we will (whether you update it and send to us, or just ask us to, we’ll do our best to accommodate and share with the greater audience). Even if additional talking points or stories that are extremely effective for you, your region, the business vertical/audience, etc, send them along so we can capture these effective materials and share the messaging. Each slide has slide notes as necessary, in multiple different sections to pay attention to: [Optional Slide] / [Required Slide]: Optional slides are used for particular topics and/or audiences. Required slides contain content that must be delivered/messaged in order to deliver the same, consistent, and effective messaging and information. This doesn’t mean you can’t alter the slide, but keep in mind the notes above for sharing modifications. [Background]: Added as necessary. Most slides won’t have/need this. [Script]: You can study this to gain knowledge on how to speak to the slide, including the story to tell. You are not required to dictate the script as written, but it is here to allow you to present the material even without extensive training/studying on the slide if necessary. [Content Notes]: Additional content, quotes, stories that may help you to formulate a more effective script for your audience. Presenter Action Items: These will be noted with [brackets] for hints or action items in areas such as: [Auto Animation]: Without clicking, this animation begins building once the slide has appeared. [Click Animation]: When to click to advance to the next animation while speaking to the slide. [Click Auto Animation]: This click signifies an auto-build-out set of animations that may take longer than expected, but allowing you to continue speaking as it builds, without continuing to click to build-out. I.e. Helpful when a text box is building out with each line delayed, versus clicking through each line manually. [Click Slide Transition]: When to click for the slide transition, or additional speaking points for during the transition between slides. [Begin Presentation Here] [Required Slide] [Background] [Script] There are many, many choices and technologies covering the Business Continuity and Disaster Recovery space for your organization and the cloud, so walk with me down the journey of getting a better understanding of what you’re doing, or trying to do today with your BC/DR strategy and why Zerto Virtual Replication is so different than what you’re used to that you just have to have it for your organization’s workloads and data. [Click Slide Transition]

We now live in a world of 24/7 business where IT has to maximize uptime & drive efficiency with hybrid clouds [Required Slide] [Background] Now that we are pushing across multiple clouds and platforms, we opening the presentation with a blanket statement that applies to the C-Level and IT/Technical level. This slide opens the conversation and frames it in a way that all audiences can agree with, and shifts their thinking right from the start, into thinking about how critical their business truly is; making them curious as to what have to say to help support this statement and fact. [Script] Your business is twenty-four-seven. Whether you are a “nine-to-five” business or not, in almost every case, you need access to your systems or data at any time and from anywhere. You may also be taking in information from orders, s, etc, so your systems cannot afford to be down. We also cannot afford the traditionally extensive maintenance and backup windows we’ve grown accustomed to in order to maintain or protect our systems and data. Our businesses need to be more efficient and be able to adopt and accelerate with new technologies such as hybrid clouds, while running at the speed of business. If you’re considering new technology without having a strategy of how that technology will embrace the cloud, you may be considering a locked-in technology that may prevent your org from growing. [Click Slide Transition] [Content Notes] “Instead of thinking of ways to minimize downtime, I’m hear to help you understand all the ways you can actually maximize uptime.”

Software-Defined Datacenter
IT Has Evolved Private, Hybrid & Public Cloud Software-Defined Datacenter [Required Slide] [Background] [Script - shorter] IT has also evolved. [Click Animation] We’ve gone from physical servers, [Click Animation] To server virtualization (which abstracted the compute layer to make servers more flexible and mobile). [Click Animation] To the “Software-Defined Datacenter” which allows for the abstraction of many more physical layers including storage, networking, security, and replication. [Click Animation] And of course, the more software-defined your business can be, the easier you can adopt and take advantage of clouds whether private, public/hosted, or a mix of these, referred to as hybrid cloud. This shift is happened all across the world in every type of organization. [Script - longer] IT has evolved. [Click Animation] Business has run on physical servers for a very long time. Everyone here is familiar with that. But of course there are inherent vulnerabilities that come with living with an entirely physical IT infrastructure. [Click Animation] So, virtualization has really started to take over by abstracting that physical compute layer in order to help businesses fix the gaps in those physical limitations of mobility, flexibility, and recoverability… [Click Animation] Then there’s the concept of the software-defined datacenter; SDDC. In the same way that virtualization made those compute resources software-defined...or not dependent on the underlying hardware, other technologies are following suit. There’s now software defined storage, networking, security, and replication. Being software defined is really all about taking those advantages of mobility, flexibility, agility, and recoverability and helps to enable the technology to now run at the speed of business. [Click Animation] That brings us to cloud computing. Making your own cloud means making your systems more software defined…and the more software defined you become the easier it is to consume more types of clouds and really puts the power and control in your hands. So, we have the private cloud, the public or hosted clouds, and combinations of clouds referred to as hybrid. This shift is happening all across the world in every type of organization. [Click Slide Transition] Virtualization Physical Servers

Zerto provides enterprise-class virtual replication and disaster recovery solutions that maximize uptime & enable a hybrid cloud strategy [Required Slide] [Background] Standard Zerto messaging slide with additional wording better focused for this presentation audience. [Script] …and Zerto provides enterprise-class virtual replication and disaster recovery solutions, enabling the business to maximize uptime for a hybrid cloud strategy. When we talk about disaster recovery the first thing that comes to most people’s mind is a natural disaster… [Click Slide Transition]

Not Just Natural Disasters
Source: Forrester Disaster Recovery Journal 2013 Not Just Natural Disasters Power Failures 26% Software Failures 9% Hardware Failures 19% Human Errors 8% Network Outages 10% Everything else, 28% [Required Slide] [Background] [Script] …but it’s not just natural disasters. [Click Auto Animation] If you look at the studies on the subject, the most likely causes of downtime are actually: power failures hardware failures network outages software failures and patching human errors… and then you have everything else, which does include separate natural disasters such as hurricanes, which is the next largest percentage behind human errors, and floods and all the other scary things like viruses and ransomware. Since 1 in 3 companies have declared a disaster in the past 5 years, it’s no longer a question of if, but when you’ll have a disaster, and you need to be able to recovery from all these different types of disasters. If you start understanding the business impact of these scenarios and correctly categorizing them as disasters, you can properly relate the costs of downtime to your business, especially if you’re not sufficiently protected. [Click Slide Transition] Did you know? 1 in 3 companies has declared a disaster in the past 5 years

Business Impact of 1 Disaster
Example $100M Annual Revenue Business Impact of 1 Disaster 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 [Required Slide] [Background] To help prevent repetitive information through multiple slides, a few slides have been combined into one concept shown in this slide. This slide is showing the business impact of one disaster and built that scenario out across multiple replication and recovery technologies. The text “data loss + downtime + data entry” depicts what factors needs to be considered when calculating the total cost. Lastly, the ZVR solution not only gives you RPO in seconds and RTO in minutes, but this same performance and low impact cost across multiple disaster/impact and recovery scenarios from any point in time. [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

How Zerto Revolutionized Replication
Hypervisor Simple, Enterprise-Class, Software-Defined Replication & Recovery Automation Servers Networking Storage Zerto Hypervisor Based Replication [Required Slide] [Background] Key point: We FIRST revolutionized replication! We revolutionized the replication technology, and then added on the orchestration and automation solution all into one. [Script] [Auto Animation] How we did this was by revolutionizing the way replication was done. Before Zerto came along, if you needed to replicate the data for disaster recovery, there was really only one way to do it at scale, and that was in the physical layer doing storage-based replication. AND it was locked-in! You would need to have 2 matching storage arrays between sites, and you’re still only just replicating the data. You weren’t getting automation and orchestration meaning you would have to do that manually or go purchase another solution (such as VMware Site Recovery Manager (SRM)) [Click Auto Animation] Zerto revolutionized replication by moving it up into the hypervisor, and by including all the automation and orchestration in one solution, it could replace everything you were trying to do before, all in one simple to use solution that also removed the lock-in to the storage, made replication and recovery completely software-defined, and most importantly again – simple. And if you look at the trend since ZVR GA’d Back in 2011, in the 5 years since, what has been happening with the other technologies? They are also moving into the hypervisor where our replication sits. We have software-defined network and security with solutions such as VMware NSX, software-defined storage using VMware Virtual SAN (VSAN). These software-defined solutions are abstracting the technology from the hardware, much like the hypervisor did for the compute resources, allowing the workloads – the business to become more flexible, agile, and cloud ready. That’s what Zerto did for replication. We’ve been doing it for 5 years; and we’re very, very good at it! [Click Slide Transition] [Content Notes] (Alternative, shorter dialogue) Back in 2011 replication in enterprise virtual environments was done at the storage layer, and at Zerto we saw this was in the wrong place as you were locked into replicating between 2 matching storage arrays. This meant that first of all you were unable to mix and match your storage between your sites, you had the complexity of replicating per lun, it was so complicated it even required a separate mgmt software for VM integration and couldn’t fully realize all the benefits of virtualization because you were tied into the physical layer. We revolutionized BC/DR by moving the replication into the hypervisor to make it software-defined and included all of the recovery automation, removing the need for a separate solution, and enabled the simplicity of protecting on a per VM basis. And Zerto isn’t alone in this trend, everything from your security, networking and storage is now moving into the hypervisor to realize the benefits of being software defined. Look at the trend since What else is now moving to the hypervisor? Networking: VMWare NSX, Storage: VMWare VSAN. Zerto has been doing this for 5 years and we are very, very good at it. Storage Replication was in the wrong place - the physical layer Replication

Resilience for Evolving IT™
Change - No lock-in, enable new tech 1 Protect - Reduce impact, test, remove risk 2 Recover - Maximize uptime, fast migrations 3 [Required Slide] [Background] Key points: Showing the full value proposition and how you can evolve, not just protecting and recovering. [Script] [Auto Animation] Because once you’ve standardize your environment on Zerto, it gives you resilience for your IT as it evolves because, first of all, you can change. Once you’ve remove that lock-in, you can be completely agnostic to the underlying storage and the underlying hypervisor. You can take on new technologies (like all-flash arrays, for example), reuse hardware when some of it is refreshed, try a new storage or hypervisor vendor…anything. [Click Animation] Maintain protection across all the VMs, storage, hypervisors…and minimize that impact to just seconds, test the recovery and remove the risk by being able to prove you can recover and go to any point-in-time. Be able to recover in minutes to maximize the uptime, and also be able to use the same software to consolidate multiple datacenters and do migrations, not just disaster recovery. Evolve and use Zerto to replicate to over 300 clouds, including Microsoft Azure and Amazon Web Services (AWS), so you can find the right provider to meet your business and industry needs as well. With all of these different use cases, you’re actually going to simplify your IT and future-proof your environment because you now have a hybrid cloud solution that allows you to easily and quickly consume all of these different services, hardware platforms, storage, hypervisors, and clouds, all from a single solution. [Click Slide Transition] [Content Notes] Change example: Asta management (UK Insurance); storage agnostic allowed cheaper storage, immediate ROI on zerto realized Protect example: Evolve - Replicate to over 300 clouds 4 Simplify - Future-proof hybrid cloud solution 5

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%

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

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

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

Disaster Recovery Automation
*Manual V2V export from Azure/AWS *Azure failback coming 2017 Disaster Recovery Automation Replicate only changes Automated Failback Configuration* Previous settings maintained Create VMs, attach vDisks, boot order Simple, Automated, Fast RTO = Minutes Networks, re-IP, scripts & validation Production Site BC/DR Site vCenter vCenter VM-Level Recovery [Required Slide] [Background] This slide walks through the use cases of failover, failover test, and migrations with the move functionality. [Script] So what does Zerto do? Whether the recovery is to production or the DR site using One-to-Many replication, as soon as you click Failover, it gives you simple automated recovery of the VMs because we’re just creating the VMs in the inventory, attaching the virtual disks to these VMs, powering them on, and automatically applying all the settings your preconfigured in your VPG settings ahead of time. This is why it’s scalable, simple, and gives you an RTO of 15 minutes or less. [Click Animation] We also allow you to test the failover. With no-impact, failover testing, you can create a simulation of this failover by booting all these VMs in an isolated environment, from any point-in-time, while still maintaining replication. NO pausing or breaking replication! This is HUGE, especially in the financial industry where they tend to be sensitive to lose your DR recoverability just because you’re running a DR test. With Zerto you don’t break your DR compliance, even during DR testing. This allows you to prove recovery, in minutes, and even during working hours. No longer do you need to call people in on the weekends for DR testing. Get your weekends back! Use Case: You don’t have to use this just for DR testing. You can use the Failover Test to verify data and recover it straight from the VM (or a mounted DB within the VM, for example). You can use this for Dev/Test – Why not run a Failover Test right in your production environment in order to test upgrades or patches, in the middle of the day, on replicas of the production VMs, before attempting to apply these patches into production?! The possibilities are endless, and true time and frustration savers! ABN AMRO in the UK -- they now use Zerto to build all of their dev/test environments, in minutes rather than weeks before Zerto, of all their applications using the Offsite Clone feature. Surrey County Council – Used Zerto (ZVR) Offsite Clone and replaced their legacy backup solution by replication all their VMs, and sending offsite clones of these VMs to offsite storage for long-term retention, saving them 800,000 pounds over the next 3 years, making Zerto not only free for them, but paying for itself many times over. Everything that makes Zerto (ZVR) great for disaster recovery is just as powerful for datacenter migrations. You click-to-move, and migrate the VMs in minutes because the replica data is only seconds behind production. The data sync finishes while the production VMs are being gracefully shutdown, and the replica VMs are recovered on the secondary site(s) with no data loss at all. You can test the move before you actually do the migration, too. I know of so many migration projects that have gone way over scope, and caused much more downtime, or extended maintenance windows, for the environment. This downtime not only extending the cost and time of your top resources for migration and troubleshooting (and rescheduling), but introducing tons of variables and room for error all at once, during the critical migration time period. Now extend this pain across multiple VMs that need to be moved together, and you will find so many complications and so much room for error. So, by scheduling some downtime (which is already way too long), you may be CAUSING even more downtime if you couldn’t test this migration ahead of time and iron out the details. Once the VMs are migrating, you can then use the exact same solution to protect these VMs for disaster recovery to another site. And then Failback – single checkbox to automatically reverse the replication, sending only the block-level changes back to production and remember all the previous settings. If you’re replicating to the public cloud – AWS or Azure today – it is a manual failback process, but on our roadmap for 2017 we’ll be adding one-click, automated failback from Azure, too. [Click Slide Transition] [Content Notes] RTO Example: A large hospital in Houston reduced their RTO for 500 mission critical servers from days and a team of 13 people running the restore to under 30 minutes with a team of 3 people completing that failover and validating success. Non-disruptive test Example: Insurance company, 250x faster DR testing with Zerto. Days to minutes. Migration Example: Woodforest bank use migrations for disaster avoidance from tornado alley. Kingfisher (UK retailer, 2000 stores) used it to consolidate datacenters across Europe. Small to large scale migrations Move Anything in Minutes Seconds of lag, test before Isolated network, restore anything Non-disruptive Failover Testing Prod & DR site w/One-To-Many

Hypervisor Integrated
Virtual awareness Real-time RPOs across all VMs KPIs, SLAs, monitoring One consistent interface Single Solution for BC/DR REST API automation & examples [Required Slide] [Background] [Script] [Click Animation] Zerto is completely integrated with your hypervisor and the key thing I want you to notice here is you can see across all your protected VMs you are shown the real-time RPO. You won’t find another solution that is going to show you this, let alone right when you login to the dashboard. What is your RPO today? Go search through your interfaces and technologies and try to piece together your RPO and exactly how much data you will lose if you were to failover right now. Zerto will give you that real-time RPO across your site, and for each Virtual Protection Group (VPG) as well. It doesn’t matter what your environment is underneath, you get the same interface every time. Of course you also use this same interface to perform and prove out your DR testing, with reports generated and all available right through this dashboard. [Click Slide Transition] [Content Notes] Ensure compliance DR Test Reporting Prove recovery capability

Prove Compliance & Remove Risk
Regulatory Compliance PCI ISO SOX HIPAA SEC [Required Slide] [Background] [Script] [Auto Animation] From the Zerto Virtual Manager (ZVM) you can run these detailed reports to prove that you can recover, how long it took, who did it, and what the outcome was. You can use this against multiple regulatory compliance standards And you can also put your own logo in the report as well. [Click Slide Transition] [Content Notes]

Monitor Anytime Anywhere
Multi-site, multi-cloud Zerto Mobile View protection across all clouds End to end security SaaS driven platform [Required Slide] [Background] Protecting across multiple datacenters and sites, while also introducing the new mobile app platform for monitoring the solution from anywhere. [Script] [Click Animation] You can use Zerto across multiple sites, multiple clouds, from one end of the country to the other, between continents, and around the world. And you can manage and monitor this with Zerto Mobile any time, from anywhere with no VPN required, and fully Secure on our new SaaS platform. You can view the health across all your clouds and datacenters in the palm of your hand. [Click Slide Transition] [Content Notes] “An oil and gas company leverages Zerto to protect hundreds of critical servers globally between datacenters and off shore rigs to ensure continuous application availability and productivity for 1000's of field and corporate employees.” If a customer wants to know if we support remote sites with low bandwidth availability, this customer example should help ease their minds.

Top Benefits of ZVR Enterprise Cloud Edition
One-To-Many Replication Replicate to Any Cloud Cross-Hypervisor Replication Multi-Tenancy & Role-Based Access Future-Proof Fully Featured One Simple Solution Zerto Product Platforms Zerto Virtual Replication Zerto Virtual Replication DRaaS Zerto Virtual Replication to Public Cloud Zerto Virtual Replication Enterprise Cloud Edition VMware vSphere l Microsoft Hyper-V Zerto Cloud Service Provider Microsoft Azure Amazon Web Services Zerto Licensing Options [Optional Slide] [Background] [Script] [Click Auto Animation] If you’re looking for the future-proof solution that will protect you across your hypervisors, to the public clouds, and to give you the huge advantages of One-to-Many replication, you want our Zerto Virtual Replication Enterprise Cloud Edition. [Click Slide Transition] [Content Notes] Yes, you can license Zerto for the individual hypervisor, but if you do want the cross-hypervisor, cloud, and One-to-Many features, you need ECE.

Zerto Licensing Options
Zerto Product Platforms Zerto Virtual Replication Zerto Virtual Replication DRaaS Zerto Virtual Replication to Public Cloud Zerto Virtual Replication Enterprise Cloud Edition VMware vSphere l Microsoft Hyper-V Zerto Cloud Service Provider Microsoft Azure Amazon Web Services Top Benefits of ZVR Enterprise Cloud Edition One-To-Many Replication Replicate to Any Cloud Cross-Hypervisor Replication Multi-Tenancy & Role-Based Access Future-Proof Fully Featured One Simple Solution [Optional Slide] [Background] [Script] [Click Auto Animation] If you’re looking for the future-proof solution that will protect you across your hypervisors, to the public clouds, and to give you the huge advantages of One-to-Many replication, you want our Zerto Virtual Replication Enterprise Cloud Edition. [Click Slide Transition] [Content Notes] Yes, you can license Zerto for the individual hypervisor, but if you do want the cross-hypervisor, cloud, and One-to-Many features, you need ECE.

ZVR Enterprise Cloud Edition
*Failback from Azure coming 2017 Feature Matrix Feature Description ZVR ZVR DRaaS ZVR to Public Cloud ZVR Enterprise Cloud Edition Unlimited Zerto Virtual Managers & Zerto Virtual Replication Appliances l Continuous Replication with RPOs in seconds from any storage to any storage Virtual Protection Group Multi-VM consistency groupings Bandwidth compression, throttling and traffic prioritization Recovery Automation for migrations, failover & failback with RTOs in minutes* No-impact recovery testing & reporting Journal based point in time recovery up to 30 days Journal file level restore Offsite backup & offsite cloning Mobile app multi-site monitoring Full REST based API automation Cross-hypervisor replication & on the fly VM conversion One-To-Many replication Replication to vSphere, Hyper-V, Azure, AWS & Zerto Cloud Service Provider Role-based access control per Virtual Protection Group Multi-tenancy & self-service portals Zerto Cloud Manager (ZCM) multi-site single pane of glass vCloud Director integration [Optional Slide] [Background] [Script] [Click Auto Animation] To break down the different features, you can see all the huge benefits of RPOs in seconds and RTOs in minutes, file-level restore, Journal-based recovery, etc. across all the editions. In order to take advantage of the numerous use cases that will greatly increase your return on investment such as keeping a local copy for dev/test or file-level recovery, faster local recovery for single-server or application failure, etc, get the Enterprise Cloud Edition. You also gain a lot more such as vCloud Director integration and the Zerto Cloud Manager portion giving a multi-site single pane of glass and RBAC (Role-Based Access Control). [Click Slide Transition] [Content Notes]

Zerto Summary Enterprise-Class Software-Defined Disaster Recovery
Journal Based Protection Recover & re-wind to the second Maximize Uptime RTO = Minutes Prove Compliance Hypervisor-based Virtual Aware Private, Hybrid & Public Clouds Powerful Data Protection & Recovery, not just VMs Storage & Hypervisor Agnostic Install & test in minutes Free trial, non-disruptive [Optional Slide] [Background] [Script] To summarize, you need: Enterprise class software for disaster recovery that is hypervisor based and fully virtual aware. Protect to multiple clouds including public, private, and hybrid. A storage and hypervisor agnostic solution that allows you to minimize the impact of an outage and rewind an entire consistency group to the second, in just minutes. This is a powerful data protection and recovery solution that installs in minutes non-disruptively using a free trial. [Click Slide Transition] [Content Notes] Minimize Impact RPO = Seconds Consistency Groupings Strategic Hybrid Cloud BC/DR Platform

Building The Business Case
Free Zerto Customized Document VMs, Applications, Tiers, Current SLAs & Risk Business Impact of Downtime & Data Loss Zerto Value & Solution Overview [Required Slide] [Background] Every single customer in the world needs to write their own business case, and we can do this with them in an automated fashion with a very powerful deliverable. We know organizations have a limited budget they are working with, or no budget at all, so we need to help them realize the total value and impact in order for them to full back their need for the Zerto solution while getting through any roadblocks. [Script] “I’m giving you the best solution along with the tools to help you get the best solution.” We know it can be hard to sell this solution internally no matter how much you want it and need to have it. We want to work with you to build this professional business case you can bring to the key stakeholders in order to prove This tool will help you build the business case as to why you need Zerto in your environment. This simple online tool is something we walk through with your to build this free document you can take with you. We build out your current list of all your applications and VMs, The current SLAs associated with each of your VMs and applications, The risk these SLAs represent to the business in the event of a disaster broken down clearly, How Zerto will bring down RPO to seconds and RTO in minutes and what that means for your return on investment for the solution, Helping you not only prove the need to business, but also to get the budget you need to buy the right technology, ultimately allowing you to cover yourself in all these situations. There aren’t many solutions that can even prove their own worth at anywhere near this capacity, and Zerto will help you prove the worth and achieve the results you’re looking for and expecting. [Click Slide Transition] [Content Notes] ROI of Zerto Investment Prove Need & Get Budget

Demo [Optional Slide] [Background]
Take 5 minutes at the end of every call if you can. Take longer if you have it! Show ZVR RPO in seconds, RTO in minutes. Show ZVR across multiple clouds and environments. Show a few clicks for failover testing, file-level recovery, VPG creation, Site Pairing, etc. [Click Slide Transition] [Content Notes]

Thank you! Contact us at contact@wisepacific.com
[Optional Slide] [Background] [Script] [Click Auto Animation] [Click Animation] [Click Slide Transition] [Content Notes]

Optional Slides

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] Same slide as earlier but without animated blocks replicating in case you need to leverage it this way for your presentation. [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%

Powerful Data Protection & Recovery
Select VM Restore Request File server data Application files SQL databases Oracle databases Exchange databases Select Files & Folders Browser download Access on ZVM Mount network share Data restored from seconds before Restore Anywhere Disks mounted No agent or impact Select point in time [Optional Slide] [Background] File-Level Restore slide is moved to optional for a key reason: It is much more powerful to SHOW JFLR within a demo using the Portable Demo Lab versus using a slide. Show this if you cannot demo it during your presentation. [Script] You can use the SAME journal and checkpoints for restoring a file or files as you use to restore a VM, a group of VMs, or a site. [Click Animation] Once you get your restore request, just launch the wizard and select the VM you want to grab the files from, click next Look through your checkpoints and select the latest copy or from all the previous point-in-time checkpoints, and click next Select all the files or folders you want to recover. This can be just a single file, or it could even be a folder or an entire database if you want to take that offline and grab whatever data you need out of the database. Then very easily click the “Download” button and the selections will download straight through your browser to your workstation. It’s as simple as that. And when you’re using the 5.0 One-to-Many feature and keeping a replica of the VMs on your local site, these file-level restores can transfer down at the speed of your local infrastructure, too! [Click Slide Transition] Recommended to show this in demo, way more powerful than slides which are showing the same process. Here if needed or demo not possible.

Enterprise Application Architectures
Firewall Load Balancers Web Servers File Servers [Optional Slide] [Background] Not required, but many presenters really like to show this slide in order to better depict the enterprise application architecture and drive home the importance of consistent point-in-time recovery across an application stack of virtual machines. [Script] Applications are typically reference as a 3-tiered object, even if all three tiers were within the same VM. Those rudimentary tiers consist of a web tier, application tier, and DB (database) tier. As we bring more and more enterprise-class services into the virtual environment, this adds many moving parts, but also gains us the ability to protect and recover all of these moving parts as one. [Click Animation] I’ll show you what I mean about an enterprise-class application. An application would usually have a firewall in front of it to keep the environment safe and secure in the environment, right? That firewall will direct network traffic to a set of network load-balancers, Which spread the traffic as best they can across multiple front-end web servers, Which talk to the application servers to bring that application functionality up to the user. There are probably multiples of these servers for redundancy, And these applications are indexing their data across a few index servers, And are getting their data from back-end database servers that are also load-balanced. And of course all of these servers need to intercommunicate, only adding to the complication and dependencies. This type of application structure is very typical and could be a little smaller or a lot larger depending on your applications and VM dependencies. You aren’t protecting them all together today because that can add a lot of complexity and confusion. But, of course you would love to be able to easily protect and recover these applications as a whole, any time you need to, right? [Click Slide Transition] [Content Notes] Index Servers Database Servers

Replication Without Consistency Groupings
Recovery Hypervisor Recovery Hypervisor Recovery Hypervisor RPO 15 Min VM1 App1 VM1 App2 VM1 App3 VM9 App1 RPO 1 Hour VM2 App1 VM5 App1 VM2 App3 VM4 App3 RPO 4 Hours VM6 App1 VM10 App1 RPO 8 Hours VM3 App1 VM3 App2 VM8 App1 VM12 App1 RPO 12 Hours VM2 App2 VM7 App1 VM5 App2 VM5 App3 [Optional Slide] [Background] [Script] Well, typical technologies like storage based LUN replication require you to place application VMs on the same LUN if you want to replicate the data consistently, and schedule a snapshot to occur on a given schedule. Well, a couple of things start to happen: (1) Data sets get larger and larger and you’re forced to now place VMs for this application across multiple LUNs, and then remember to manage the replication schedules so they occur at the same time for recovery consistency. (2) Once that data rate of change begins to grow too large for the replication window, you must RAISE your RPO by adding more time in between each replication schedule in order to allow for all of the data to send before the next snapshot takes place and needs to be replicated. [Click Animation] So, VMs for the same application are now spread across multiple replication schedules, which doesn’t seem like THAT big of a deal, until it comes time to recover them. They are all from different points-in-time, looking for data or changes that aren’t going to exist where they are expected, and this add a LOT of cost, through TIME, to you. Time for people to recover the data to a certain point-in-time Time for people to repair the recovered data so it can start to even be useable And MORE time for people to RE-ENTER all the lost data, if that can even be done. Of course, you’re also losing the TIME/MONEY of incoming transactions, plus the time your employees are losing while being pulled away from their day job to help through this recovery process. You now need to multiply these issues across many applications, and good luck managing the placement and replication schedule! You have these pain points today, but may be just accepting them because: It’s what you’re used to, You didn’t know there was a better way that is still affordable, or even more affordable than what you’re using today. There is no consistent recovery and this is totally not scalable. [Click Slide Transition] RPO 24 Hours+ VM4 App1 VM4 App2 VM3 App3 VM11 App1 No Consistent Recovery = Unscalable

Replication With Consistency Groupings
Recovery Hypervisor Recovery Hypervisor Recovery Hypervisor RPO 4 Seconds VM1 App1 VM2 App1 VM3 App1 VM4 App1 VM5 App1 VM6 App1 VM7 App1 VM8 App1 VM9 App1 VM10 App1 VM11 App1 VM12 App1 RPO 6 Seconds RPO 8 Seconds VM1 App2 VM2 App2 VM3 App2 VM4 App2 VM5 App2 RPO 10 Seconds RPO 12 Seconds VM1 App3 VM2 App3 VM3 App3 VM4 App3 VM5 App3 [Optional Slide] [Background] [Script] [Click Animation] With Zerto Virtual Replication, you place all the VMs you want to protect and recover together into the same consistency group, no matter what LUN or storage they are on, and the data will replicate continuously and give you recovery point-in-time checkpoints each time the data across all these VMs is consistent with write-order fidelity. You may also notice here that these numbers are drastically different from the previous slide where we had replication schedules from 15 minute, to hours, or a day between them, to these VPG RPOs being within seconds each. [Click Slide Transition] [Content Notes] RPO 14 Seconds Consistent Recovery = Scalable

300+ Clouds Geographic Coverage 3000+ Customers All Verticals
Strategic Solution 300+ Clouds Geographic Coverage Customers All Verticals 600+ Partners Trusted Advisors [Optional Slide] [Background] If you want to show this, you can, but it is typically more powerful to talk about the various customer use cases as you run through the presentation as a whole versus just showing this slide. [Script] Since then we have doubled our customer base year on year Added 300 cloud service providers utilizing Zerto for DRaaS Signed 600 channel partners trained on the Zerto solution [Click Slide Transition]

Why ZVR Doesn’t Need VSS
Picture (snapshot) vs video (ZVR) Constantly moving target (changing blocks) How to capture it consistently? Picture = stand still (quiesce, VSS) If not still, picture = inconsistent Video = record real-time (tracking, replicating & write ordering) Result = VSS not required Re-wind to checkpoints every few seconds No snapshots & consistent recovery [Optional Slide] [Background] If an audience questions application consistency and wants to know about VSS and why Zerto customers don’t even need it (nor use it, but they can), this slide visually walks through how the standard ZVR technology is actually better and more desirable. If we can’t describe this slide correctly, you can almost bet most other people won’t be able to describe the lack-of-need of actually using VSS versus ZVR native protection across a VPG. [Script] [Auto Animation] How do you capture a clean state of data that is constantly moving? You keep trying as the data is flying by, but you’re always getting a blur between blocks or “frames” in the context of using a camera to capture playing children… [Click Animation] You CAN’T, unless you can PAUSE the data! Who wants to pause their data? How do you capture this paused data across multiple VMs? With ZVR, think of it as a video recorder always capturing the data movement (changes) versus using a camera, asking your subject to hold still, and taking a picture from one single-point-in-time on a single VM. Now you can just rewind to any point-in-time before your business impact occurred, to ensure you have a clean and consistent recovery point, without EVER impacting that production VM. Take this thought and remember we also allow you to do this across many VMs if you so desire, by placing them in the same protection group. Now you have point-in-time recovery across an application stack of VMs without worrying about data loss of recoverability. [Click Slide Transition] [Content Notes]

The Fastest DR Solution To Microsoft Azure
Simultaneous local & multi-remote One-To-Many Replication, RPO = Seconds Pre-config VPN Gateway, Express Route Replica data in storage account Azure Marketplace Deployed ZCA Cost effective, no recovery VMs until needed Production Site One-To-Many [Optional Slide] [Background] Introducing One-to-Many replication to a specific destination type. Use this slide in case you don’t want to show replication to all the various clouds, but just to Azure. For a different 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 sites, 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] 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 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. *Note: One-To-Many requires ECE licensing, covered later in deck. Recover VMs, files & folders Restore Anything In Minutes Local & remote recovery Multi-SLA journal retention On-Premises & Hybrid Cloud DR All-in-one solution, drive cloud efficiency

Enterprise-Class Replication To AWS
Simultaneous local & multi-remote One-To-Many Replication, RPO = Seconds Pre-config VPN to VPC, Direct Connect Replica data in S3 bucket All-In-One Zerto Cloud Appliance (ZCA) Cost effective, no recovery VMs until needed Production Site One-To-Many [Optional Slide] [Background] Introducing One-to-Many replication to a specific destination type. Use this slide in case you don’t want to show replication to all the various clouds, but just to AWS. For a different 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 AWS, 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] 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. *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 In Minutes Local & remote recovery Multi-SLA journal retention On-Premises & Hybrid Cloud DR All-in-one solution, drive cloud efficiency

Enterprise-Class Replication DRaaS To ZCSP
Simultaneous local & multi-remote One-To-Many Replication, RPO = Seconds Pre-config VPN or MPLS Replica data as VMDKs Zerto Cloud Connector (ZCC) Cost effective, no recovery VMs until needed Production Site One-To-Many [Optional Slide] Background] Introducing One-to-Many replication to a specific destination type. Use this slide in case you don’t want to show replication to all the various clouds, but just to Zerto Cloud Service Providers (ZCSP). For a different 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 Zerto Cloud Service Provider sites, 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] 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 In Minutes Local & remote recovery Multi-SLA journal retention On-Premises & Hybrid Cloud DR All-in-one solution, drive cloud efficiency

Reduce The Cost Of DR With Zerto & Azure
Utilizing power, cooling, hardware, licenses Expensive Physical BC/DR Site Locked into datacenter lease Only pay for what you use DRaaS to Public Cloud Flexibility of monthly billing [Optional Slide] [Background] Why an organization would consider DR to Azure to reduce the cost of DR. [Script] How can you realize the cost savings when replicating to Azure? [Click Animation] Here we are replicating one on-premises datacenter to another on-premises. This is expensive because you not only have a site to own or lease and maintain, but also the costs of power, cooling, licenses, etc, of the technology within your datacenter. You are also locked into that site, limited where you can run your workloads. Or when you can move them somewhere else. You have unpredictable capex and opex costs because not only do you also need to go through the server and storage refreshes every few years, but your DR solution is probably also consuming a large chunk of the IT budget. When you are looking at Disaster Recovery as a Service (DRaaS) to the Azure cloud, you have the flexibility of monthly billing and only pay for what you use. This gives you predictable and low opex and capex costs without the need for management of the infrastructure. You IT budget is only needed for the service improvement as necessary. [Click Slide Transition] Server & storage refreshes Unpredictable High CAPEX costs IT budget consumed by DR No cost of Server & storage refreshes Predictable Low OPEX cost IT budget for service improvement

Reduce The Cost Of DR With Zerto & AWS
Utilizing power, cooling, hardware, licenses Expensive Physical BC/DR Site Locked into datacenter lease Only pay for what you use DRaaS to Public Cloud Flexibility of monthly billing [Optional Slide] [Background] Why an organization would consider DR to AWS to reduce the cost of DR. [Script] How can you realize the cost savings when replicating to AWS? [Click Animation] Here we are replicating one on-premises datacenter to another on-premises. This is expensive because you not only have a site to own or lease and maintain, but also the costs of power, cooling, licenses, etc, of the technology within your datacenter. You are also locked into that site, limited where you can run your workloads. Or when you can move them somewhere else. You have unpredictable capex and opex costs because not only do you also need to go through the server and storage refreshes every few years, but your DR solution is probably also consuming a large chunk of the IT budget. When you are looking at Disaster Recovery as a Service (DRaaS) to the AWS cloud, you have the flexibility of monthly billing and only pay for what you use. This gives you predictable and low opex and capex costs without the need for management of the infrastructure. You IT budget is only needed for the service improvement as necessary. [Click Slide Transition] Server & storage refreshes Unpredictable High CAPEX costs IT budget consumed by DR No cost of Server & storage refreshes Predictable Low OPEX cost IT budget for service improvement

Reduce Costs with DRaaS
Utilizing power, cooling, hardware, licenses Expensive Physical BC/DR Site Locked into datacenter lease Only pay for what you need DRaaS to BC/DR Site Flexibility to migrate +300 [Optional Slide] [Background] Why an organization would consider DR to a ZCSP to reduce the cost of DR. [Script] How can you realize the cost savings when replicating to a Zerto Cloud Service Provider (ZCSP)? [Click Animation] Here we are replicating one on-premises datacenter to another on-premises. This is expensive because you not only have a site to own or lease and maintain, but also the costs of power, cooling, licenses, etc, of the technology within your datacenter. You are also locked into that site, limited where you can run your workloads. Or when you can move them somewhere else. You have unpredictable capex and opex costs because not only do you also need to go through the server and storage refreshes every few years, but your DR solution is probably also consuming a large chunk of the IT budget. When you are looking at Disaster Recovery as a Service (DRaaS) to the ZCSP cloud, you have the flexibility of monthly billing and only pay for what you use. This gives you predictable and low opex and capex costs without the need for management of the infrastructure or managing or performing the DR tasks when using a managed cloud provider. You IT budget is only needed for the service improvement as necessary. [Click Slide Transition] Server & storage refreshes Unpredictable High CAPEX costs Hidden costs of management No cost of Server & storage refreshes Predictable Low OPEX cost Managed service removing hidden costs

AWS Use-Cases Install in minutes, per-VM, simple to use
Initial sync, no snapshots no impact, leave running Efficient AWS use of S3 Storage & EC2 Instances Consistent, RPO seconds, RTO minutes, PIT recovery No-impact migration or recovery testing [Optional Slide] [Background] [Script] Let’s have a look at why people are using Amazon Web Services (AWS) for DRaaS… [Click Animation] You can be up and running in minutes, on a per-VM basis, and it’s simple to use. There is no impact to the protected VM even during the initial sync. It’s the same hypervisor-based solution and doesn’t require snapshots or agents. We take advantage of the efficiencies and cost savings of AWS S3 Storage and EC2 Instances. You will use the consistent look and feel of what you are using total with the Zerto solution, and still get RPOs in seconds, RTOs in minutes, and remote Journals for point-in-time recovery. Test failover anytime you want with no impact to production VMs and no impact to the continuous replication. You easily can choose to migrate your workloads into AWS after you’ve fully tested the process. Easily migrate tens to hundreds of VMs simultaneously! Zerto gives you the complete solution for BC/DR and migrations to AWS [Click Slide Transition] Migrate tens to hundreds of VMs simultaneously Complete BC/DR & Migration to AWS

ROI for DRaaS to AWS 50 25 $378,024 $97,486 $280,538 -74% 100 $602,466
ROI calculated using AWS tool: No cost of running EC2 instances, other than ZCA 3 year Zerto licensing included Protected VMs Storage/TB On Premise AWS Saving Percentage 50 25 $378,024 $97,486 $280,538 -74% 100 $602,466 $176,300 $426,166 -71% 200 $1,122,360 $333,928 $788,432 -70% 400 $2,188,920 $648,750 $1,540,170 800 $4,322,038 $1,273,985 $3,048,053 [Optional Slide] [Background] [Script] AWS also provides an only tool to help you calculate your ROI. You will take advantage of having no costs of running EC2 instances other than the ZCA, because with this solution, the VMs are created and booted on the fly, attached to their replica data disks. [Click Animation] Here are some example figures that seem too good to be true, but believe it. You can easily start realizing the savings today over any other solution you’re comparing. [Click Slide Transition]

Enable Shared Services
Self-Service & Multi-tenancy Application Owner Department Business Unit Organization [Optional Slide] [Background] [Script] With the included Zerto Self-Service Portal, you can achieve self-service multitenancy to separate your workload replication and maintain role-based-access control (RBAC) by application owner, department, business units, or organizations. [Click Slide Transition]

One-To-Many Replication Use Cases
Protect a VM in multiple VPGs Full replica, journal with RPO in seconds Per VPG SLAs, journal retention Recover applications to BC/DR site Restore files & VMs direct to production Powerful local data protection Protect to cloud, longer retention All-In-One Solution [Optional Slide] [Background] [Script] The new One-to-Many functionality in ZVR 5.0 brings exciting power allowing you to have multiple SLAs for individual VMs, meeting the needs of all your use cases and organizational needs. Protect a single VM in multiple VPGs (Virtual Protection Groups) You get a full replicate and Journal for each, and each with RPOs in seconds Decide, per VPG, the journal & recovery settings, giving you control over multiple SLAs on a per-VM basis. A VM could replicate to a local site destination with a 4-day Journal for extremely fast testing and file-level recovery, and also the ability to quickly redeploy an impacted VM. You could also replicate that same VM to a remote site or cloud with a different Journal retention policy, maybe 30-days, in order to have longer retention utilize the cheaper storage advantage of the cloud economies of scale. You can recover applications locally or to a DR site, or just use your DR site for migration testing or full site recovery. While using your local site to restore files, VMs, and an application in a stack of VMs directly into production. This gives you powerful local data protection while still having the ability of longer retention, further away in the cloud. All of this, with one simple solution. [Click Slide Transition] Local Copy Production Site BC/DR Site

Use Cases – Who Uses Zerto?
Financial 1 Healthcare 2 Commercial 3 Industrial 4 Education 5 [Optional Slide] [Background] [Script] [Auto Animation] So who can use Zerto Virtual Replication for their organization? Anyone, across all verticals: With 15+ VMs to protect, with the perpetual licensing. Lower VM count when using DRaaS. The minimum number of VMs to protect can be lower when working with a Zerto Cloud Service Provider. [Click Slide Transition]

Zerto Use Cases Migrations with subsequent DR
New BC/DR solution with low RPOs/RTOs Simplifying BC/DR with Always-On Protection & Virtual Awareness Replication VMware > Hyper-V or Hyper-V to VMware Multi-site and multi-tenant BC/DR Replace & improve Storage Replication Upsell to SRM customers to rip & replace Upgrade from Veeam Replication [Optional Slide] [Background] [Script] Let’s have a look the most common use cases our customers are using ZVR… [Click Animation] You need a new BC/DR solution and are looking for low RPOs and RTOs You need to simplify your BC/DR strategy and operations with a solution that’s always on and has that virtual awareness you’ve been trying to design and work around. Maybe you need and easy way to replace and improve your current storage replication, which may also mean replacing some storage in your infrastructure without introducing the disruptions and architecture complications you’ll find with traditional solutions. Often times SRM customers come to us because they are ready for something more scalable, with RPOs and RTOs that are actually achievable. So, they install ZVR alongside and quickly realize it’s time for a change. Easily replicate between disparate SAN vendors, meaning you can reuse old hardware, or even try out those sparkly new all-flash arrays without making the investment or risk of replacing them all, everywhere just yet. Easily migrate between datacenters, to the cloud, or even between hypervisors or hypervisor versions. AND, once the workloads are migrated, you have the perfect solution to protect those VMs in the new location. Take advantage of crossing hypervisor vendors. Think of all the time you spend now on projects just worrying about the costs, versions, and planning around keeping everything the same everywhere. What if you acquire a company running Hyper-V and you’re a VMware shop? How long will that take you today to migrate those workloads into your VMware environment? Well, with Zerto you can replicate them in, fully test them ahead of time in your environment, and move them in minutes when you’re confident in the move. Maybe you want to run Hyper-V in your remote offices to take advantage of the lower costs for fewer workloads, but you need to replicate them into your main datacenter running VMware. We work very well side-by-side with Veeam. They have an excellent backup solution and Zerto can first augment this with replication and DR protection. You may quickly realize that using the ZVR Journal for file-level recovery and extremely fast recovery for all the other situations, that you may no longer even need to keep the Veeam solution in place with that additional cost, overhead, and operations. Upgrade from guest-base replication solutions so you can gain the speed, recovery points, scalability, and virtual awareness that you aren’t going to get with a guest-based solution. [Click Slide Transition] Replication between different SAN vendors Upgrade from Guest Based solutions

Business Impact of 1 Disaster
Example $10M Annual Revenue Business Impact of 1 Disaster RPO 24 Hours Daily Backups RTO 24 Hours Impact $82,191 Snapshot Replication RPO 4 Hours RTO 4 Hours Impact $13,968 Zerto Virtual Replication RPO 20 Seconds RTO 15 Minutes Impact $298 Data Loss + Downtime + Data Entry 5pm 9am [Required Slide] [Background] To help prevent repetitive information through multiple slides, a few slides have been combined into one concept shown in this slide. This slide is showing the business impact of one disaster and built that scenario out across multiple replication and recovery technologies. The text “data loss + downtime + data entry” depicts what factors needs to be considered when calculating the total cost. Lastly, the ZVR solution not only gives you RPO in seconds and RTO in minutes, but this same performance and low impact cost across multiple disaster/impact and recovery scenarios from any point in time. [Script] [Click Auto Animation] And if you look at the business impact of just 1 disaster, take a company with an annual revenue of $10M 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 $100M annual revenue business instead of a $10M annual revenue business. Re-wind and recover anything in minutes, from any point in time, direct to production or recovery site

Optional Cloud Specific Slides

Zerto DRaaS & Intra Cloud Architecture
For each customer & cloud vCenter/SCVMM Zerto Virtual Manager (ZVM) & VRAs Install in minutes Manager of managers Zerto Cloud Manager vCD, multi-tenancy, resource mgmt Customer A DRaaS Cloud BC/DR Cloud vCenter ZVM VM VRA VM VRA vCenter ZVM ZCM ZVM vCenter ZCC vCD VPN, MPLS ZCC Customer B VRA VRA VRA VRA SCVMM ZVM [Optional Slide] [Background] [Script] Let’s take a look at the architecture when replicating to remote sites or even managed clouds. [Click Animation] You’ll still locally deploy the ZVM and VRAs, which install in minutes without disruptions within your environment. The remote cloud provider will also be running ZVMs and VRAs. The cloud provider uses Zerto Cloud Manager (ZCM) to give you multitenancy and RBAC. They could even be running vCloud Director (vCD) on top of their vSphere environment (as can you, locally). The Zerto cloud replication network also consists of dedicated portgroups for your workloads and replication traffic. And when replicating to a multitenant environment, each customer will have a Zerto Cloud Connector (ZCC) deployed within the provider site, allowing you and isolated replication and management network [Click Slide Transition] VM VRA VM VRA For DRaaS multi-tenancy, 1 per customer Zerto Cloud Connector (ZCC) 2 IPs, 1 customer facing 1 replication network Deploy dedicated port group Zerto Cloud Replication Network Standard or distributed switch

Simple Management With Zerto Cloud Manager
One pane of glass view of environment Centralizes BC/DR Management across cloud and customer sites Accelerate customer onboarding [Optional Slide] [Background] [Script] Zerto Cloud Manager gives you: A single-pane of glass across your environment Centralized management across cloud and customer sites And makes it easier for you to accelerate customer onboarding [Click Slide Transition]

Fast Integration - Zerto Self-Service Portal
Self-service for DRaaS & Intra-Cloud Integrate into existing portals with single sign-on Permissions for view, edit, test, move & failover Full REST APIs [Optional Slide] [Background] [Script] The Zerto Self-Service Portal allows for: Self-service for DRaaS to the cloud and intra-cloud Can integrate into existing portals with single sign-on Allows you to set permissions for access to view, edit, test, move, and failover And has a full set of REST APIs for additional automation and integration [Click Slide Transition]

Billing & Resource Planning
Ensure Accurate Billing with Automation Collect information on a per ZVM basis Export data for automated billing # of protected VMs Exact storage and bandwidth MEM/CPU resource information Manage SLAs [Optional Slide] [Background] [Script] Complete and integrated billing and resource planning allows you to: Collect information on a per ZVM basis And export the data for automated billing including: # of protected VMs Exact storage and bandwidth consumed RAM and CPU resource information Helping you to manage your SLAs [Click Slide Transition]

Hybrid Cloud: The Future of the Enterprise
Hybrid Cloud Market by 2018 $107B Public Cloud Market by 2017 “As Private Cloud Matures, Hybrid Cloud is Next” Gartner 70% [Optional Slide] [Background] [Script] The Hybrid Cloud is the Future of the Enterprise 70% if enterprises will be using the hybrid cloud by 2015! Yes, yesterday’s news, right? But you are, aren’t you? Maybe you’ve tried it and decided you love it, maybe trying it helped you decide what workloads you want to run in the cloud versus locally…but either way, you’re using it, or going to soon, and you shouldn’t have to deal with the pain points and struggles of trying it for production workloads, BC/DR destinations, or migrations to the cloud. Enable the flexibility and mobility for your always-on business with IT Resilience provided by Zerto. [Click Slide Transition] * Gartner, IDC, MarketsandMarkets Of Enterprises will Pursue Hybrid Cloud by 2015

Zerto Virtual Replication 5.0

Similar presentations

Presentation on theme: "Zerto Virtual Replication 5.0"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Zerto Virtual Replication 5.0

Similar presentations

Presentation on theme: "Zerto Virtual Replication 5.0"— Presentation transcript:

Similar presentations

About project

Feedback