MV_BACKUP_HISTORY

This view stores information about backups that have been made.

Column	Description
`BACKUP_ID`	A unique identifier for the backup.
`CLUSTER_NAME`	Name of the cluster that carried out the backup.
`CLUSTER_ID`	Unique id that can identify a cluster (see `show cluster id`).
`DATABASE_NAME`	Name of the database that was backed up.
`START_TIMESTAMP`	Timestamp at which the backup started.
`END_TIMESTAMP`	Timestamp at which the backup completed.
`NUM_PARTITIONS`	Number of partitions for the backup.
`BACKUP_PATH`	Path to where the backup file was placed after backup completed.
`CHECKSUM`	Concatenated CRC32C checksum of all backup files. Refer to Verifying Full Backup Files for more information.
`STATUS`	Status of backup - Success or Failure.
`SIZE`	For full backups: size of all backup files, in megabytes. For incremental backups: size of the changes (the incremental differences), in megabytes.
`INCR_BACKUP_ID`	A unique identifier for an incremental backup. If the backup is a full backup instead of an incremental backup, `incr_backup_id` is `NULL`.
`TYPE`	Type of backup. Possible values are `FULL`, `INCR_INIT`, `INCR_DIFF`, `SPLIT_PARTITIONS`, or an empty string. An empty string indicates that the type of backup is unknown because the backup was performed in earlier versions of SingleStore, when the backup type was not recorded in the `MV_BACKUP_HISTORY` table.
`TAGS`	The values of `TAGS` parameter if it is specified in the `BACKUP DATABASE` command.
`SERVER_VERSION`	The SingleStore version.
`MEMORY_USAGE`	The amount of memory (MB) used by the database before performing a backup.
`IMPLEMENTATION`	The type of backup: `Lockfree` or `Original`.
`LOCKFREE_TIMESTAMP`	The global logical timestamp used to perform the backup if implementation is `Lockfree`.

Example - this query shows the last successful backup:

SQL

SELECT backup_id, database_name, backup_path, lockfree_timestamp FROM information_schema.mv_backup_history 
  WHERE status = 'Success' AND implementation = 'Lockfree' ORDER BY backup_id;

Note: information_schema.MV_BACKUP_HISTORY is populated only when the BACKUP DATABASE command is run to create a database backup.

MV_BACKUP_HISTORY

Was this article helpful?

Was this article helpful?