Join Percona’s, Technical Services Manager, Jervin Real as he presents Lock, Stock and Backup: Data Guaranteed on Wednesday, August 16, 2017 at 7:00 am PDT / 10:00 am EDT (UTC-7).
Backups are crucial in a world where data is digital and uptime is revenue. Environments are no longer bound to traditional data centers, and span multiple cloud providers and many heterogeneous environments. We need bulletproof backups and impeccable recovery processes. This talk aims to answer …
[Read more]Background on Backup Locks
I was very excited to see Backup locks support in release notes for the latest Percona XtraDB Cluster 5.6.21 release. For those who are not aware, backup locks offer an alternative to FLUSH TABLES WITH READ LOCK (FTWRL) in Xtrabackup. While Xtrabackup can hot-copy Innodb, everything else in MySQL must be locked (usually briefly) to get a consistent snapshot that lines up with Innodb. This includes all other storage engines, but also things like table schemas (even on Innodb) and async replication binary logs. You can skip this lock, but it isn’t …
[Read more]
TL;DR version: The backup locks feature introduced in Percona
Server 5.6.16-64.0 is a lightweight alternative to FLUSH
TABLES WITH READ LOCK and can be used to take both
physical and logical backups with less downtime on busy servers.
To employ the feature with mysqldump, use
mysqldump --lock-for-backup --single-transaction.
The next release of Percona XtraBackup will also be using backup
locks automatically if the target server supports the
feature.
Now on to the gory details, but let’s start with some history.
In the beginning…
In the beginning there was FLUSH TABLES, and users
messed with their MyISAM tables under a live server and were not
ashamed. Users could do nice things like:
mysql> FLUSH TABLES; # execute myisamchk, myisampack, backup / restore some tables, etc.
And users were happy until someone realized that tables must be …
[Read more]