How CloudEndure Disaster Recovery Works

1 How CloudEndure Disaster Recovery Works How CloudEndure Disaster Recovery Works The Technology Behind CloudEndure 's Enterprise-Grade Disaster Recovery Solution Introduction CloudEndure Disaster Recovery utilizes block-level, Continuous CloudEndure Disaster Recovery into Amazon Web Services Data Replication, which ensures that target machines are spun (AWS) is a Software-as-a-Service (SaaS) solution. The solution up in their most up-to-date state during a Disaster or drill. is powered by innovative workload mobility technology, which Organizations can thereby achieve sub-second Recovery Point continuously replicates applications from physical, virtual, or Objectives (RPOs). cloud-based infrastructure to a low-cost staging area (detailed below) that is automatically provisioned in any target AWS Region The Continuous Data Replication takes place in a low-cost staging of the customer's choice.

2 During failover or testing, an up-to-date area in AWS, which reduces compute and storage footprint to copy of applications can be spun up on demand and be fully a minimum. In the event of a Disaster , CloudEndure triggers a functioning in minutes. highly automated machine conversion process (p2c/v2c/c2c) and a scalable orchestration engine that can spin up thousands of Enterprises use CloudEndure to replicate their most critical machines in the target AWS Region within minutes. This enables databases, including Microsoft SQL server , Oracle, and MySQL, as organizations to achieve Recovery Time Objectives (RTOs) of well as enterprise applications such as SAP. CloudEndure Disaster minutes. Accordingly, CloudEndure 's Disaster Recovery solution Recovery enables rapid Recovery of the application, database, files, provides the resilience of a warm standby solution at the low OS configuration, and system state meaning that operations cost of a cold standby solution.

3 Continue smoothly with fully functioning workloads. In addition to a self-service, web-based Console with centralized management Benefits of CloudEndure Disaster Recovery include: for all of a customer's projects, CloudEndure provides APIs that Significant reduction in total cost of ownership (TCO). enable developers to implement large-scale automation and compared to traditional Disaster Recovery solutions other advanced capabilities. Sub-second Recovery Point Objectives (RPOs). Recovery Time Objectives (RTOs) of minutes Benefits of CloudEndure Disaster Recovery Support for any source infrastructure and any workload, including critical databases such as Microsoft SQL server , CloudEndure Disaster Recovery enables organizations to quickly Oracle, and MySQL, and enterprise applications such as SAP.

4 And easily shift their Disaster Recovery strategy to AWS from Automated failover to target AWS Region during a Disaster existing physical or virtual data centers, private clouds, or other Point-in-time Recovery , enabling failover to earlier versions of public clouds, in addition to supporting cross-region Disaster replicated servers in cases of data corruption, ransomware, Recovery in AWS. or other malicious attacks 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. 1. How CloudEndure Disaster Recovery Works One-click failback, restoring operations to source servers Google Cloud Platform (GCP), Oracle Cloud, IBM Cloud, automatically OpenStack, and others Unlimited, non-disruptive Disaster Recovery drills Replication is also supported between Regions or Availability Zones in AWS.

5 Continuous Data Replication Once installed and activated, the CloudEndure Agent begins At the core of CloudEndure 's technology is our proprietary initial replication, reading all of the data on the machines at Continuous Data Replication engine, which provides real- the block level and replicating it to a low-cost staging area that time, asynchronous, block-level replication. is automatically provisioned in a customer's AWS account, in a target network of their choice. Customers define replication CloudEndure replication is done at the OS level (rather than settings, such as subnets, security groups, and replication tags, hypervisor or SAN level), enabling support of the following through the self-service, web-based CloudEndure Console.

6 Types of source infrastructure: The initial replication can take anywhere from several minutes to Physical machines, including both on-premises and co- several days, depending on the amount of data to be replicated location data centers and the bandwidth available between the source infrastructure Virtual machines from any hypervisor, including VMware, and the target AWS Region. No reboot is required nor is there Microsoft Hyper-V, and others system disruption throughout the initial replication. Cloud-based machines, including AWS, Microsoft Azure, After the initial replication is complete, the source machines are CloudEndure Console Replication Settings Customers select source infrastructure and target AWS. Region, subnets, security groups, and more from the CloudEndure Console before beginning initial replication.

7 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. 2. How CloudEndure Disaster Recovery Works continuously monitored to ensure constant synchronization, Low-Cost Staging Area in Target up to the last second. Any changes to source machines are AWS Region asynchronously replicated in real time into the AWS staging area.. CloudEndure maintains ongoing replication of source machines into a low-cost staging area in the customer's Unlike snapshot-based replication, Continuous Data preferred target AWS Region. The staging area contains cost- Replication enables customers to continue normal IT. effective resources automatically provisioned and managed by operations during the entire replication process without CloudEndure to receive the replicated data without incurring performance disruption or data loss.

8 Significant costs. These resources include a small number of lightweight VMs (each supporting multiple source machines), Continuous Data Replication allows customers to achieve disks (one target disk for each replicating source disk), and sub-second Recovery Point Objectives (RPOs), as the data snapshots. is always up-to-date and ready to be spun up as soon as a Disaster strikes. Whereas traditional Disaster Recovery solutions require duplicate hardware, compute, storage, networking, and CloudEndure 's replication engine is application-agnostic, software licenses in order to ensure data integrity and sub- supporting all application types, including databases and second RPO, CloudEndure 's staging area eliminates the need legacy applications, any source infrastructure, and a wide for duplicate provisioning of resources and thus significantly array of operating systems.

9 Reduces the TCO for Disaster Recovery . The fully provisioned Recovery environment, with the right-sized compute and higher CloudEndure Console List of Machines &. Data Replication Progress The CloudEndure Console provides real-time information on the data replication status of each machine. Customers can add machines, conduct drills, and launch failovers and failbacks right from the Console. 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. 3. How CloudEndure Disaster Recovery Works performance storage required for recovered workloads, is and machine properties. Automated orchestration combined only launched during a Disaster or a DR drill. with machine conversion (detailed below) enables customers to achieve Recovery Time Objectives (RTOs) of minutes.

10 Automated Orchestration of Target AWS. Environment Customers are able to select configuration settings for how machines will be provisioned (orchestrated) in the target AWS. CloudEndure 's orchestration engine automatically launches Region, instance/machine type, subnet, security groups, and fully operational workloads in the target AWS Region at elastic IP in the CloudEndure Console. the time of failover or test. This automated process includes cloning disks from the staging area to target networks and Automated Machine Conversion provisioning all additional resources such as VMs, network interfaces, and firewalls. When replicating machines across similar infrastructure, such as between AWS Regions or Availability Zones, the replicated The entire orchestration process typically takes minutes, machines can boot natively in the target environment, as depending on the general time it takes the machines to boot.