mysql.backup_progress table lets you
monitor backup jobs as they run, and the
mysql.backup_history table lets you see the
results of completed jobs. Because these tables are created with
the CSV storage engine, you can query them from SQL, or parse the
text files from an application or script.
To skip updating these tables for a backup operation, use the
Each row in the
backup_progress table records a
state change or message from a running backup job. The
backup_progress table has the following
Because the CSV storage engine cannot represent
NULL values directly, the logs use a -1 value
instead, for example in the
if binary logging is not enabled.
backup_id value to group together the
information for a single backup operation, and to correlate with
the corresponding row in the
table after the job is finished.
error_message values to track the progress of
the job, and detect if a serious error occurs that requires
stopping the backup operation.
current_state values to measure how long each
part of the backup operation takes, to help with planning the time
intervals for future backups.
Each row in the
backup_history table records
the details of one completed backup job, produced by
mysqlbackup command. The
backup_history table has the following columns:
end_lsn value to automate operations
related to incremental backups. When you take a full or
incremental backup, you can specify the end LSN from that backup
as the starting LSN for the next incremental backup with the
start-lsn option (an alternative to
specifying the start LSN value is to use the
Use the values that correspond to backup-related configuration
settings, such as
backup_destination, to confirm that the backups
are using the right source and destination directories.
Use the values
last_error_code to evaluate the success or
failure of each backup.
the backup operation was successful. In case of any errors, you
can retrieve the full list of errors for that backup operation