Sign inTry Free

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.

ERROR_CODE

Error code for failed backups.

ERROR_MESSAGE

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_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.

Last modified: June 26, 2023

Was this article helpful?

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK