Taking Backups in Replication Environments¶
There are options specific to back up from a replication replica.
innobackupex --slave-info¶
This option is useful when backing up a replication replica server. It prints the
binary log position and name of the source server. It also writes this
information to the xtrabackup_slave_info file as a CHANGE MASTER
statement.
This is useful for setting up a new replica for this source can be set up by
starting a replica server on this backup and issuing the statement saved in the
xtrabackup_slave_info file. More details of this procedure can be found
in How to setup a replica for replication in 6 simple steps with Percona XtraBackup.
innobackupex –safe-slave-backup¶
In order to assure a consistent replication state, this option stops the replica
SQL thread and waits to start backing up until Slave_open_temp_tables in
SHOW STATUS is zero. If there are no open temporary tables, the backup will
take place, otherwise the SQL thread will be started and stopped until there are
no open temporary tables. The backup will fail if Slave_open_temp_tables
does not become zero after innobackupex –safe-slave-backup-timeout
seconds (defaults to 300 seconds). The replica SQL thread will be restarted when
the backup finishes.
Using this option is always recommended when taking backups from a replica server.
Note
Make sure your replica is a true replica of the source before using it as a source for backup. A good tool to validate a replica is pt-table-checksum.
Contact us
For free technical help, visit the Percona Community Forum.
To report bugs or submit feature requests, open a JIRA ticket.
For paid support and managed or consulting services , contact Percona Sales.
