.. _storing_history:
====================================
Store backup history on the server
====================================
|Percona XtraBackup| supports storing the backups history on the server. This feature was implemented in |Percona XtraBackup| 2.2. Storing backup history on the server was implemented to provide users with additional information about backups that are being taken. Backup history information will be stored in the :ref:`PERCONA_SCHEMA.XTRABACKUP_HISTORY ` table.
To use this feature three new |innobackupex| options have been implemented:
* :option:`innobackupex --history` = : This option enables the history feature and allows the user to specify a backup series name that will be placed within the history record.
* :option:`innobackupex --incremental-history-name` = : This option allows an incremental backup to be made based on a specific history series by name. |innobackupex| will search the history table looking for the most recent (highest ``to_lsn``) backup in the series and take the ``to_lsn`` value to use as it's starting lsn. This is mutually exclusive with :option:`innobackupex --incremental-history-uuid`, :option:`innobackupex --incremental-basedir` and :option:`innobackupex --incremental-lsn` options. If no valid LSN can be found (no series by that name) |innobackupex| will return with an error.
* :option:`innobackupex --incremental-history-uuid` = : Allows an incremental backup to be made based on a specific history record identified by UUID. |innobackupex| will search the history table looking for the record matching UUID and take the ``to_lsn`` value to use as it's starting LSN. This options is mutually exclusive with :option:`innobackupex --incremental-basedir`, :option:`innobackupex --incremental-lsn` and :option:`innobackupex --incremental-history-name` options. If no valid LSN can be found (no record by that UUID or missing ``to_lsn``), |innobackupex| will return with an error.
.. note::
Backup that's currently being performed will **NOT** exist in the xtrabackup_history table within the resulting backup set as the record will not be added to that table until after the backup has been taken.
If you want access to backup history outside of your backup set in the case of some catastrophic event, you will need to either perform a ``mysqldump``, partial backup or ``SELECT`` * on the history table after |innobackupex| completes and store the results with you backup set.
Privileges
----------
User performing the backup will need following privileges:
* ``CREATE`` privilege in order to create the :ref:`PERCONA_SCHEMA.xtrabackup_history ` database and table.
* ``INSERT`` privilege in order to add history records to the :ref:`PERCONA_SCHEMA.xtrabackup_history ` table.
* ``SELECT`` privilege in order to use :option:`innobackupex --incremental-history-name` or :option:`innobackupex --incremental-history-uuid` in order for the feature to look up the ``innodb_to_lsn`` values in the :ref:`PERCONA_SCHEMA.xtrabackup_history ` table.
.. _xtrabackup_history:
PERCONA_SCHEMA.XTRABACKUP_HISTORY table
---------------------------------------
This table contains the information about the previous server backups. Information about the backups will only be written if the backup was taken with :option:`innobackupex --history` option.
.. list-table::
:header-rows: 1
:widths: 20 40
* - Column Name
- Description
* - uuid
- Unique backup id
* - name
- User provided name of backup series. There may be multiple entries with the same name used to identify related backups in a series.
* - tool_name
- Name of tool used to take backup
* - tool_command
- Exact command line given to the tool with --password and --encryption_key obfuscated
* - tool_version
- Version of tool used to take backup
* - ibbackup_version
- Version of the xtrabackup binary used to take backup
* - server_version
- Server version on which backup was taken
* - start_time
- Time at the start of the backup
* - end_time
- Time at the end of the backup
* - lock_time
- Amount of time, in seconds, spent calling and holding locks for ``FLUSH TABLES WITH READ LOCK``
* - binlog_pos
- Binlog file and position at end of ``FLUSH TABLES WITH READ LOCK``
* - innodb_from_lsn
- LSN at beginning of backup which can be used to determine prior backups
* - innodb_to_lsn
- LSN at end of backup which can be used as the starting lsn for the next incremental
* - partial
- Is this a partial backup, if ``N`` that means that it's the full backup
* - incremental
- Is this an incremental backup
* - format
- Description of result format (``file``, ``tar``, ``xbstream``)
* - compact
- Is this a compact backup
* - compressed
- Is this a compressed backup
* - encrypted
- Is this an encrypted backup
Limitiatons
-----------
* :option:`innobackupex --history` option must be specified only on the innobackupex command line and not within a configuration file in order to be effective.
* :option:`innobackupex --incremental-history-name` and :option:`innobackupex --incremental-history-uuid` options must be specified only on the innobackupex command line and not within a configuration file in order to be effective.