MariaDB database solutions, including MariaDB Enterprise Server, ColumnStore, Xpand and MariaDB SkySQL support comprehensive disaster recovery strategies for restoring availability and data in the event of an unexpected outage or data loss/corruption – everything from multiple data centers to backup and restore tools to flashback and system versioning.
MariaDB Enterprise Backup can restore a complete database or individual table using a combination of full and incremental backups, and leverages a sequence of non-blocking backup stages to allow writes and schema changes while tables are being backed up.
If data has been wrongly deleted or modified recently, MariaDB Flashback can roll back the last transactions to restore the database to a point in time right before the data was deleted or modified – a lot faster than restoring a database from one or more backups.
MariaDB database solutions support precise point-in-time recovery using MariaDB Enterprise Backup to restore data from one or more backups and the binary log to roll forward transactions since the last backup until the specified point in time is reached.
MariaDB database solutions can use delayed replication to prevent recent, unwanted changes (e.g., an incorrect update) from propagating to one or more replicas, allowing one of them to be temporarily promoted to primary while the changes are rolled back on the previous primary.
MariaDB database solutions can preserve data before it is updated or deleted by creating and maintaining historical copies of rows as they are modified, allowing DBAs to restore a row to a previous state using the results of point-in-time query on its history.
MariaDB database solutions can be deployed to a secondary data center, or in multi- and hybrid-cloud topologies, using asynchronous replication and separate, asymmetric clusters, optionally with delayed replication, or with full multi-master clustering for maximum disaster recovery.
When it comes to disaster recovery, the ideal reference architecture depends on the recovery point objective and recovery time objective as well as business and application requirements regarding high availability, performance and consistency. The reference architecture below uses clustering in the primary data center for high availability and asynchronous replication to the secondary for performance. In addition, while the primary data center uses separate databases with delayed replication for backups and system versioning, the secondary uses a scaled down deployment with a primary/replica topology and system versioning.
In this webinar, we'll provide an in-depth overview of the disaster recovery tools and capabilities available in MariaDB Enterprise Server, and share best practices for creating a comprehensive disaster recovery strategy.Watch Now