Skip to main content
This page describes the support Cockroach Labs provides for restoring backups across major versions of CockroachDB. The sections outline the support for the most common use cases when restoring backups across versions:
Since CockroachDB considers the cluster version when running a backup, this page refers to versions in a “v24.1.x” format. For example, both v24.1.1 and v24.1.2 are considered as v24.1 clusters for backup purposes.
Because CockroachDB is designed with high fault tolerance, backups are primarily needed for . However, taking regular backups of your data is an operational best practice. When upgrading to a major release, we recommend of your cluster. See .

​
Support for restoring backups into a newer version

Cockroach Labs supports restoring a backup taken on a cluster on a specific major version into a cluster that is on the same version or the next major version. Therefore, when upgrading your cluster from version N to N+1, if you took a backup on major version N, you can restore it to your cluster on either major version N or N+1. Additionally, you can skip an version when restoring a backup. Innovation releases are intermediate releases that introduce new features, but are not long-term supported versions. Other than skipping innovation releases, restoring backups outside major version N or N+1 is not supported. For example, backups taken on v24.1.x can be restored into v24.3.x (skipping the v24.2 innovation release). Backups taken on v24.3.x can be restored into v25.1.x: Refer to and Upcoming releases. When a cluster is in a mixed-version state during an upgrade, will fail. See the for the necessary steps to finalize your upgrade. For CockroachDB Cloud clusters, see the page.
Cockroach Labs does not support restoring backups from a higher version into a lower version.

​
Support for long-term backup archival

When you need to archive a backup for the long term, we recommend that you also archive the CockroachDB binary of the version that the backup was taken on. For a true archival copy that is not dependent on CockroachDB at all, running a changefeed to export your data from CockroachDB and archiving the files would be a better approach instead of taking a backup. See for more detail.

​
See also