MV_ BACKUP_ HISTORY
Warning
SingleStore 9.0 gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 8.9 is recommended for production workloads, which can later be upgraded to SingleStore 9.0.
This view stores information about backups that have been made.
Column |
Description |
---|---|
|
A unique identifier for the backup. |
|
Name of the cluster that carried out the backup. |
|
Unique id that can identify a cluster (see |
|
Name of the database that was backed up. |
|
Timestamp at which the backup started. |
|
Timestamp at which the backup completed. |
|
Number of partitions for the backup. |
|
Path to where the backup file was placed after backup completed. |
|
Concatenated CRC32C checksum of all backup files. Refer to Verifying Full Backup Files for more information. |
|
Status of backup - Success or Failure. |
|
For full backups: size of all backup files, in megabytes. For incremental backups: size of the changes (the incremental differences), in megabytes. |
|
A unique identifier for an incremental backup. |
|
Possible values are |
|
The values of |
|
The SingleStore version. |
|
The amount of memory (MB) used by the database before performing a backup. |
|
The type of backup: |
|
The global logical timestamp used to perform the backup if implementation is |
|
Error code for failed backups. |
|
Error message for failed backups. |
Example - this query shows the last successful backup:
SELECT backup_id, database_name, backup_path, lockfree_timestamp FROM information_schema.mv_backup_historyWHERE status = 'Success' AND implementation = 'Lockfree' ORDER BY backup_id;
Note: information_
is populated only when the BACKUP DATABASE
command is run to create a database backup.
Last modified: June 26, 2023