Tag: RPO

Many public sector organizations that are moving to the cloud often misunderstand that the architecture of AWS Regions and Availability Zones fundamentally changes how they should think about disaster recovery and resiliency. In this blog post, I share some best practices to answer common questions about building highly available workloads, and share some ways to consider high availability, disaster recovery, and application resiliency within AWS.

Applications running on LAMP (Linux, Apache, MySQL, and PHP) stack are ubiquitous—WordPress alone represents 38% of all content management systems. Because of the popularity of these applications, public sector organisations such as educational institutions should protect their business continuity by implementing disaster recovery (DR) solutions: policies, tools, and procedures to help the recovery or continuation of technology infrastructure and systems following a disaster. AWS Professional Services created a business continuity solution for on-premises LAMP applications that could eliminate the need for physical backup infrastructure and improve recovery time. The solution was recently piloted by Cardiff University.

Nobody wants to lose data—and setting a Recovery Point Objective (RPO) to zero makes this intent clear. Customers with government mission-critical systems often need to meet this requirement, since any amount of data loss will cause harm. RPO covers both resilience and disaster recovery—everything from the loss of an individual physical disk to an entire data center. Existing systems support RPO zero through a combination of architecture patterns (including resilient messaging) and on-premises legacy databases. Frequently interpreted as a database or storage requirement, providing for RPO zero requires thinking about the entire system. To do so, you can use AWS services and architecture patterns, which provide resilience to failure with clustering, auto scaling, and failover across multiple data centers within one region.

In October 2018, the Florida panhandle was hit by Hurricane Michael, a Category 5 storm that set a new record for the strongest hurricane on record to make landfall in the area. Florida State University (FSU) already understood the need for a long-term continuity of operations plan, and the devastation Michael wrought on the surrounding areas solidified how critical a disaster recovery (DR) service is to their overall operations. Disaster-recovery-as-a-service (DRaaS) is the business world’s advanced solution to unexpected disruption. Whether the threat comes from natural disaster, technical failure, human error, or malicious action, the result is still unplanned downtime and the need for recovery. Learn how FSU designed and launched their DRaaS solution on an accelerated timeline while optimizing costs.