Understand backup locking stages. This page explains how mariadb-backup uses BACKUP STAGE statements to minimize locking during operation.
The BACKUP STAGE statements make it possible to make an efficient external backup tool. How mariadb-backup uses these statements depends on whether you are using the version that is bundled with MariaDB Community Server or the version that is bundled with MariaDB Enterprise Server.
BACKUP STAGE in MariaDB Community ServerThe BACKUP STAGE statements are supported. However, the version of mariadb-backup that is bundled with MariaDB Community Server does not yet use the BACKUP STAGE statement in the most efficient way. mariadb-backup simply executes the following BACKUP STAGE statement to lock the database:
When the backup is complete, it executes the following BACKUP STAGE statement to unlock the database:
BACKUP STAGE in MariaDB Community ServerCopy some transactional tables.
InnoDB (i.e. ibdataN and file extensions .ibd and .isl)
Copy the tail of some transaction logs.
BACKUP STAGE START in MariaDB Community Servermariadb-backup from MariaDB Community Server does not perform any tasks in the START stage.
BACKUP STAGE FLUSH in MariaDB Community Servermariadb-backup from MariaDB Community Server does not currently perform any tasks in the FLUSH stage.
BACKUP STAGE BLOCK_DDL in MariaDB Community Servermariadb-backup from MariaDB Community Server does not currently perform any tasks in the BLOCK_DDL stage.
BACKUP STAGE BLOCK_COMMIT in MariaDB Community Servermariadb-backup from MariaDB Community Server performs the following tasks in the BLOCK_COMMIT stage:
Copy other files.
i.e. file extensions .frm, .isl, .TRG, .TRN, .opt, .par
BACKUP STAGE END in MariaDB Community Servermariadb-backup from MariaDB Community Server performs the following tasks in the END stage:
Copy the MyRocks checkpoint into the backup.
BACKUP STAGE in MariaDB Enterprise ServerThe following sections describe how the MariaDB Backup version of mariadb-backup that is bundled with MariaDB Enterprise Server uses each statement in an efficient way.
BACKUP STAGE START in MariaDB Enterprise Servermariadb-backup from MariaDB Enterprise Server performs the following tasks in the START stage:
Copy all transactional tables.
InnoDB (i.e. ibdataN and file extensions .ibd and .isl)
Aria (i.e. aria_log_control and file extensions .MAD
BACKUP STAGE FLUSH in MariaDB Enterprise Servermariadb-backup from MariaDB Enterprise Server performs the following tasks in the FLUSH stage:
Copy all non-transactional tables that are not in use. This list of used tables is found with SHOW OPEN TABLES.
MyISAM (i.e. file extensions .MYD and .MYI)
MERGE
BACKUP STAGE BLOCK_DDL in MariaDB Enterprise Servermariadb-backup from MariaDB Enterprise Server performs the following tasks in the BLOCK_DDL stage:
Copy other files.
i.e. file extensions .frm, .isl, .TRG, .TRN, .opt, .par
BACKUP STAGE BLOCK_COMMIT in MariaDB Enterprise Servermariadb-backup from MariaDB Enterprise Server performs the following tasks in the BLOCK_COMMIT stage:
Create a MyRocks checkpoint using the rocksdb_create_checkpoint system variable.
Copy changes to system log tables.
mysql.general_log
mysql.slow_log
BACKUP STAGE END in MariaDB Enterprise Servermariadb-backup from MariaDB Enterprise Server performs the following tasks in the END stage:
Copy the MyRocks checkpoint into the backup.
This page is licensed: CC BY-SA / Gnu FDL
The tail of the InnoDB redo log (i.e. ib_logfileN files) are copied for InnoDB tables.
Copy some transactional tables.
Aria (i.e. aria_log_control and file extensions .MAD and .MAI)
Copy the non-transactional tables.
MyISAM (i.e. file extensions .MYD and .MYI)
MERGE (i.e. file extensions .MRG)
ARCHIVE (i.e. file extensions .ARM and .ARZ)
CSV (i.e. file extensions .CSM and .CSV)
Create a MyRocks checkpoint using the rocksdb_create_checkpoint system variable.
Copy the tail of some transaction logs.
The tail of the InnoDB redo log (i.e. ib_logfileN files) are copied for InnoDB tables.
Save the binary log position to xtrabackup_binlog_info.
Save the Galera Cluster state information to xtrabackup_galera_info.
.MAICopy the tail of all transaction logs.
The tail of the InnoDB redo log (i.e. ib_logfileN files) are copied for InnoDB tables.
The tail of the Aria redo log (i.e. aria_log.N files) are copied for Aria tables.
.MRGARCHIVE (i.e. file extensions .ARM and .ARZ)
CSV (i.e. file extensions .CSM and .CSV)
Copy the tail of all transaction logs.
The tail of the InnoDB redo log (i.e. ib_logfileN files) are copied for InnoDB tables.
The tail of the Aria redo log (i.e. aria_log.N files) are copied for Aria tables.
Copy the non-transactional tables that were in use during BACKUP STAGE FLUSH.
MyISAM (i.e. file extensions .MYD and .MYI)
MERGE (i.e. file extensions .MRG)
ARCHIVE (i.e. file extensions .ARM and .ARZ)
CSV (i.e. file extensions .CSM and .CSV)
Check ddl.log for DDL executed before the BLOCK DDL stage.
The file names of newly created tables can be read from ddl.log.
The file names of dropped tables can also be read from ddl.log.
The file names of renamed tables can also be read from ddl.log, so the files can be renamed instead of re-copying them.
Copy changes to system log tables.
mysql.general_log
mysql.slow_log
This is easy as these are append only.
Copy the tail of all transaction logs.
The tail of the InnoDB redo log (i.e. ib_logfileN files) are copied for InnoDB tables.
The tail of the Aria redo log (i.e. aria_log.N files) are copied for Aria tables.
This is easy as these are append only.
Copy changes to statistics tables.
mysql.table_stats
mysql.column_stats
mysql.index_stats
Copy the tail of all transaction logs.
The tail of the InnoDB redo log (i.e. ib_logfileN files) are copied for InnoDB tables.
The tail of the Aria redo log (i.e. aria_log.N files) are copied for Aria tables.
Save the binary log position to xtrabackup_binlog_info.
Save the Galera Cluster state information to xtrabackup_galera_info.
BACKUP STAGE START;
BACKUP STAGE BLOCK_COMMIT;BACKUP STAGE END;