Disaster Recovery Planning for MySQL & MariaDB

1 . Disaster Recovery Planning for MySQL & MariaDB Bart Oles Severalnines 

2 .

3 .Copyright 2017 Severalnines AB 

4 .Free to download Initial 30 days Enterprise trial Converts into free Community Edition Enterprise / paid versions available Copyright 2017 Severalnines AB 

5 . Automation & Management Deployment (Free Community) Management (Paid Features) ● Deploy a Cluster in Minutes ● Backup Management ○ On-Prem ● Upgrades & Patching ○ Cloud (AWS/Azure/Google) - paid ● Security & Compliance Monitoring (Free Community) ● Operational Reports ● Systems View with 1 sec Resolution ● Automatic Recovery & Repair ● DB / OS stats & Performance Advisors ● Performance Management ● Configurable Dashboards ● Automatic Performance Advisors ● Query Analyzer ● Real-time / historical Copyright 2017 Severalnines AB 

6 .Supported Databases Copyright 2017 Severalnines AB 

7 .Our Customers Copyright 2017 Severalnines AB 

8 . Agenda Business Considerations for Disaster Recovery ○ Is 100% uptime possible Disaster Recovery Tiers ○ Analyzing risk ○ No offsite data ○ Assessing business impact ○ Database with no Hot Site ○ Database with Hot Site Defining Disaster Recovery ○ Asynchronous replication to Hot Site ○ Outage Timeline ○ Synchronous replication to Hot Site ○ RTO ○ RPO ○ RTO + RPO = ? 

9 . Copyright 2017 Severalnines AB Business Considerations for Disaster Recovery Copyright 2018 Severalnines AB 

10 . What is Disaster Recovery? Policies, tools & procedures that ensure your data is secure and protected in case of an outage or serious catastrophe ● Failures ○ Operational (power, network, IT systems) ○ Natural (hurricane, flood, fire, earthquake) ○ Human caused (operator error, malicious activity, terrorism) ● Drivers ○ How fast can we get up and running ○ What data have we lost ○ How can we reduce risk 

11 .Uptime Guarantees - Why Compromise? 

12 .The Small Print 

13 .“We Offer 100% Availability, But We Exclude… “ ● Planned outages ○ e.g., server or network maintenance ● Failure of network, power or facilities delivered by an upstream provider ● DOS attacks, hacker activity or other malicious events ● Acts of God ○ e.g., weather related - hurricane, flood 

14 .Low Downtime Comes at a Cost 

15 .Analyzing Risk 

16 .Assessing Business Impact 

17 .Defining Disaster Recovery Copyright 2017 Severalnines AB Copyright 2018 Severalnines AB 

18 .Stockholm to Oslo Train Breaks Down After One Hour x 

19 .Outage Timeline 

20 .Recovery Time Objective (RTO) 

21 .Recovery Point Objective (RPO) 

22 . RTO + RPO = 0 ? Load Balancing Database Data Integrity Replication Storage Network File Clustering DB Clustering Bonding Replication Security 

23 .“Everything Fails, All the Time” Werner Vogels 

24 . Disaster Recovery Tiers Copyright 2017 Severalnines AB Copyright 2018 Severalnines AB 

25 .Cost of Disaster Recovery 

26 .Matching Disaster Recovery Plans to the Business 

27 . Backup with No Hot Site ● Physical vs Logical backup ○ High impact on RTO ● Combine Full & Incremental ○ PITR-compatible to reduce RPO ● Schrödinger’s backup ○ “The condition of any backup is unknown until a restore is attempted” ● Encryption ● Keep a copy of latest backup in active site 

28 .Backup Retention ● Local Server ○ Up to 1 week ● Local Datacenter ○ Up to 2 weeks ● Remote Datacenter ○ Up to 4 weeks ○ Plus keep monthly backups & annual backups as required 

29 . Backup with Hot Site ● We can reinstall DBs and apps from scratch and restore data ● Recovery time predictable ● In case of AWS, pre-configured AMIs can be used to quickly provision the application environment