Take Full and Incremental Backups

On this page

Because CockroachDB is designed with high fault tolerance, backups are primarily needed for disaster recovery (i.e., if your cluster loses a majority of its nodes). Isolated issues (such as small-scale node outages) do not require any intervention. However, as an operational best practice, we recommend taking regular backups of your data.

There are two main types of backups:

• Full backups
• Incremental backups

You can use the BACKUP statement to efficiently back up your cluster's schemas and data to popular cloud services such as AWS S3, Google Cloud Storage, or NFS, and the RESTORE statement to efficiently restore schema and data as necessary. For more information, see Use Cloud Storage for Bulk Operations.

Backup collections

A backup collection defines a set of backups and their metadata. The collection can contain multiple full backups and their subsequent incremental backups. The path to a backup is created using a date-based naming scheme and stored at the URI passed with the BACKUP statement.

In the following example, a user has taken weekly full backups and nightly incremental backups to their collectionURI:

Collection:
|—— 2022
  |—— 02
    |—— 09-155340.13/
      |—— Full backup files
      |—— 20220210/
        |—— 155530.50/
          |—— Incremental backup files
      |—— 20220211/
        |—— 155628.07/
          |—— Incremental backup files
      [...]
    |—— 16-143018.72/
      |—— Full backup files
      |—— 20220217/
        |—— 155530.50/
          |—— Incremental backup files
      |—— 20220218/
        |—— 155628.07/
          |—— Incremental backup files
      [...]

SHOW BACKUPS IN {collectionURI} will display a list of the full backup subdirectories in the collection's storage location.

A locality-aware backup is a specific case where part of the collection data is stored at a different URI. The backup collection will be stored according to the URIs passed with the BACKUP statement: BACKUP INTO LATEST IN {collectionURI}, {localityURI}, {localityURI}. Here, the collectionURI represents the default locality.

In the examples on this page, {collectionURI} is a placeholder for the storage location that will contain the example backup.

Full backups

Full backups are now available to both core and Enterprise users.

Full backups contain an un-replicated copy of your data and can always be used to restore your cluster. These files are roughly the size of your data and require greater resources to produce than incremental backups. You can take full backups as of a given timestamp. Optionally, you can include the available revision history in the backup.

In most cases, it's recommended to take nightly full backups of your cluster. A cluster backup allows you to do the following:

• Restore table(s) from the cluster
• Restore database(s) from the cluster
• Restore a full cluster

Backups will export Enterprise license keys during a full cluster backup. When you restore a full cluster with an Enterprise license, it will restore the Enterprise license of the cluster you are restoring from.

Take a full backup

To perform a full cluster backup, use the BACKUP statement:

> BACKUP INTO '{collectionURI}';

To restore a backup, use the [RESTORE][restore.html] statement, specifying what you want to restore as well as the collection's URI:

• To restore the latest backup of a table:

  > RESTORE TABLE bank.customers FROM LATEST IN '{collectionURI}';
  

• To restore the latest backup of a database:

  > RESTORE DATABASE bank FROM LATEST IN '{collectionURI}';
  

• To restore the latest backup of your full cluster:

  > RESTORE FROM LATEST IN '{collectionURI}';
  

  Note:

  A full cluster restore can only be run on a target cluster that has never had user-created databases or tables.

• To restore a backup from a specific subdirectory:

  > RESTORE DATABASE bank FROM {subdirectory} IN '{collectionURI}';
  

To view the available backup subdirectories, use SHOW BACKUPS.

Incremental backups

If your cluster grows too large for nightly full backups, you can take less frequent full backups (e.g., weekly) with nightly incremental backups. Incremental backups are storage efficient and faster than full backups for larger clusters.

Incremental backups are smaller and faster to produce than full backups because they contain only the data that has changed since a base set of backups you specify (which must include one full backup, and can include many incremental backups). You can take incremental backups either as of a given timestamp or with full revision history.

Take an incremental backup

Periodically run the BACKUP command to take a full backup of your cluster:

> BACKUP INTO '{collectionURI}';

Then, create nightly incremental backups based off of the full backups you've already created. To append an incremental backup to the most recent full backup created in the given destination, use LATEST:

> BACKUP INTO LATEST IN '{collectionURI}';

For an example on how to specify the destination of an incremental backup, see Incremental backups with explicitly specified destinations.

If it's ever necessary, you can then use the [RESTORE][restore.html] command to restore your cluster, database(s), and/or table(s). Restoring from incremental backups requires previous full and incremental backups.

To restore from the most recent backup, run the following:

> RESTORE FROM LATEST IN '{collectionURI}';

To restore a specific backup, run RESTORE with the backup's subdirectory:

> RESTORE FROM '{subdirectory}' IN '{collectionURI}';

Incremental backups with explicitly specified destinations

To explicitly control where your incremental backups go, use the INTO {subdirectory} IN (destination) syntax:

> BACKUP DATABASE bank INTO '{subdirectory}' IN '{collectionURI}' \
    AS OF SYSTEM TIME '-10s' \
    WITH revision_history;

A full backup must be present in the destination for an incremental backup to be stored in a subdirectory. If there isn't a full backup present in the destination when taking an incremental backup, one will be taken and stored in the destination.

Examples

The following examples make use of:

• Amazon S3 connection strings. For guidance on connecting to other storage options or using other authentication parameters instead, read Use Cloud Storage for Bulk Operations.
• The default AUTH=specified parameter. For guidance on using AUTH=implicit authentication with Amazon S3 buckets instead, read Use Cloud Storage for Bulk Operations — Authentication.

Automated full backups

Both core and Enterprise users can use backup scheduling for full backups of clusters, databases, or tables. To create schedules that only take full backups, include the FULL BACKUP ALWAYS clause. For example, to create a schedule for taking full cluster backups:

> CREATE SCHEDULE core_schedule_label
  FOR BACKUP INTO 's3://{BUCKET NAME}/{PATH}?AWS_ACCESS_KEY_ID={KEY ID}&AWS_SECRET_ACCESS_KEY={SECRET ACCESS KEY}'
    RECURRING '@daily'
    FULL BACKUP ALWAYS
    WITH SCHEDULE OPTIONS first_run = 'now';

     schedule_id     |        name         | status |         first_run         | schedule |                                                                                       backup_stmt
---------------------+---------------------+--------+---------------------------+----------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  588799238330220545 | core_schedule_label | ACTIVE | 2020-09-11 00:00:00+00:00 | @daily   | BACKUP INTO 's3://{BUCKET NAME}/{PATH}?AWS_ACCESS_KEY_ID={KEY ID}&AWS_SECRET_ACCESS_KEY={SECRET ACCESS KEY}' WITH detached
(1 row)

For more examples on how to schedule backups that take full and incremental backups, see CREATE SCHEDULE FOR BACKUP.

Advanced examples

For examples of advanced BACKUP and RESTORE use cases, see:

• Incremental backups with a specified destination
• Backup with revision history and point-in-time restore
• Locality-aware backup and restore
• Encrypted backup and restore
• Restore into a different database
• Remove the foreign key before restore
• Restoring users from system.users backup

See also

• BACKUP
• RESTORE
• Take and Restore Encrypted Backups
• Take and Restore Locality-aware Backups
• Take Backups with Revision History and Restore from a Point-in-time
• SQL DUMP
• IMPORT
• Use the Built-in SQL Client
• Other Cockroach Commands

Was this helpful?