Many organizations implement high availability for their Microsoft SQL Server machines. However, this is not sufficient for organizations that require true IT resilience. In order to avoid data loss and downtime of mission-critical Microsoft SQL Server databases, enterprise-grade disaster recovery is a necessity. Disaster recovery helps you avoid the high costs that come with an IT disaster, such as regulatory fines, lost business, and damage to your reputation.
There are different approaches to disaster recovery. Traditional disaster recovery for Microsoft SQL Server databases requires duplication of infrastructure, operating systems (OS), and Microsoft SQL Server software, rendering it a highly expensive IT project that is also a challenge to maintain. In addition to incurring large expenses, this approach has another disadvantage: it can replicate only the database itself, but not the other components of the application, which is critical to recovering the entire application.
CloudEndure Disaster Recovery enables a more modern approach to protecting Microsoft SQL Server databases: cloud-based disaster recovery into AWS. CloudEndure Disaster Recovery not only leverages the cloud to significantly reduce disaster recovery infrastructure costs, it also enables rapid recovery of Microsoft SQL Server machines and the entire machine state by replicating the OS and all of the database, application, and system files running on the machine. In addition, CloudEndure Disaster Recovery uses ACID-compliant crash-consistent replication, meaning that your operations continue to run smoothly with fully operational workloads and consistent data. In cases where uninterrupted business continuity is critical, this difference means that you can affordably achieve recovery times of minutes, rather than hours or days.
- Support of all Microsoft SQL Server versions and editions
- Support of Always On availability groups and failover cluster instances (FCIs)
- Block-level, continuous replication of Microsoft SQL Server machines, including the OS and all databases
- Support of geographically remote target sites
- Automated machine conversion and application stack orchestration, including recovery order support
- Quick, non-disruptive installation
- Support for raw device mapping (RDM) disks
- Web-based control with centralized management console
- Automated disaster recovery drills without performance impact
- Simple failover and failback
- One disaster recovery solution for all Microsoft SQL Server versions and editions, third-party software, and OS
- Crash-consistent technology keeps data consistent
- Significant savings on disaster recovery
- RPO of seconds and RTO of minutes
- Increased reliability and high tolerance for network instability
- Point-in-time recovery for data corruption or cyber attacks
- Support of all source infrastructure, including on-premises physical and virtual infrastructure, public clouds, and other AWS Regions
- Enterprise-grade security
CloudEndure Disaster Recovery architecture
CloudEndure Disaster Recovery maintains continuous, asynchronous replication of the disks into a low-cost staging area located in your target AWS Region. This eliminates the need for additional costly appliances or separate operational databases, and reduces your compute, storage, and software licensing footprint to a minimum. In the event of a disaster, use CloudEndure Disaster Recovery to trigger an automated large-scale orchestration and machine conversion process. CloudEndure Disaster Recovery will recover each source machine running Microsoft SQL Server databases to a single Amazon EC2 instance, with recovery point objectives (RPOs) of seconds and recovery time objectives (RTOs) of minutes. You can deploy CloudEndure Disaster Recovery from any physical, virtual, or cloud-based source.
Reduce total cost of ownership (TCO)
CloudEndure Disaster Recovery enables you to significantly reduce your disaster recovery TCO compared to traditional disaster recovery solutions. CloudEndure Disaster Recovery is more cost-efficient than most legacy replication tools, and enables recovery for the entire OS, including all of its applications. This means that you can use CloudEndure Disaster Recovery for all of your enterprise workloads, in addition to your Microsoft SQL Server databases.
Infrastructure — When using CloudEndure Disaster Recovery, there is no need to pay for duplicate hardware, compute, or networking for a target site. A continuously replicating version of all your data is kept up to date on AWS, utilizing low-cost storage and lightweight compute. The more expensive recovery environment, using high-performance storage and actual compute to run the application, is only used when launched during a disaster or drill. In comparison, application-specific solutions require duplicate hardware, compute, high-performance storage, and networking.
OS licenses — In order for most disaster recovery solutions to provide robust recovery of your Microsoft SQL Server databases, you need to purchase duplicate OS and Microsoft SQL Server licenses to run your Microsoft SQL Server databases in your standby site. With CloudEndure Disaster Recovery, you don’t need to purchase duplicate OS licenses. Your Microsoft SQL Server databases and all other server data are kept in sync in a dormant staging area that is not running any licensed OS or application. In the event of a disaster or drill, your machine will be launched on demand and converted to run natively on AWS. You will only pay for what you use during the disaster period, according to the Amazon EC2 BYOL (“bring your own license”) model for Microsoft SQL Server. In other words, you get robust resilience with RPOs of seconds and RTOs of minutes, at the cost of a cold standby solution.
Geographic redundancy — Best practice for disaster recovery is to use a target site that is located in a different geographic region than the source environment. Short distances between source and target sites can be problematic from a regulatory perspective. CloudEndure Disaster Recovery enables the use of a target site in a remote geographic location while still performing continuous data replication with minimal RPO and RTO. You can implement geographic redundancy between on-premises and AWS, across different AWS Regions, and between a different cloud provider and AWS.
High tolerance for network instability — CloudEndure Disaster Recovery is designed to keep data in sync, asynchronously, over long distances, regardless of database write rates or network conditions. In contrast, legacy database replication tools are designed to be used within a data center with low network latencies, and are not designed to replicate data across long distances. If you have a write-intensive system, your tolerance for network interruptions is very low.
Replicate any application from any source infrastructure
Any application — CloudEndure Disaster Recovery replicates and recovers all Microsoft SQL Server versions and editions running on AWS-supported OS. In addition, CloudEndure Disaster Recovery natively supports replication of other applications, including third-party software, legacy applications, homegrown applications, OS, and common enterprise applications such as SAP, Microsoft Exchange Server, and Microsoft SharePoint. Application-specific disaster recovery solutions only protect Microsoft SQL Server, meaning that you would need to use a separate replication solution for the rest of your applications, the OS, system state configuration, and files.
Any source — CloudEndure Disaster Recovery performs equally efficient replication and recovery for all Microsoft SQL Server versions and editions running on x86-based Windows and Linux OS versions. This includes Microsoft SQL Server databases running on any physical, virtual, or cloud-based infrastructure.
Block-level replication — CloudEndure Disaster Recovery utilizes block-level replication rather than taking snapshots or writing data to disk. This is what enables data integrity for Microsoft SQL Server databases as well as their OS and surrounding applications.
Perform automated disaster recovery testing
Easy implementation — A strong disaster recovery strategy must include the capability for frequent testing. However, many organizations do not perform testing or drills on a regular basis due to the overhead needed to do so, or concerns that testing or a failed drill will disrupt their production environment or even cause data loss. CloudEndure Disaster Recovery enables automated disaster recovery testing for all of your Microsoft SQL Server databases, thereby eliminating time-intensive manual processes such as log shipping. During a drill, use CloudEndure Disaster Recovery to launch machines in your target AWS Region in complete isolation to avoid network conflicts and performance impact on your source environment. Application-specific disaster recovery solutions do not provide automated testing.
Non-disruptive testing — You can quickly and easily conduct frequent, non-disruptive drills that launch your Microsoft SQL Server databases and all other workloads in your target AWS Region without impacting your source environment. This increases the reliability of your disaster recovery strategy for Microsoft SQL Server. All changes that take place in your source environment during the tests are saved and replicated.
Enable data integrity
Crash consistent – CloudEndure Disaster Recovery complements ACID-compliant Microsoft SQL Server technology in order to keep your data consistent at all times. When your Microsoft SQL Server databases are spun up in recovery mode on AWS during a disaster, all of your partial transactions will automatically be rolled back, allowing operations to continue with consistent data.
Point-in-time recovery – This functionality enables failover to earlier versions of replicated servers, which is particularly important for ransomware attacks or IT environment corruptions, where the latest version of system data has been compromised.
Enterprise-grade security – CloudEndure Disaster Recovery is ISO 27001 compliant, and enables the highest level of security standards by using AES 256-bit data encryption both in transit and at rest. Replication traffic is transmitted directly from your source servers to your target AWS Region, and can be restricted to your private networks for better security, speed, and control.