From e8ffb981fca46a0ad1a1b13e66047ff61658cdbf Mon Sep 17 00:00:00 2001 From: Joe Lodin Date: Mon, 20 Apr 2026 16:21:19 -0400 Subject: [PATCH] Update docs for cross-tenant Basic/Standard restore support --- .../backups/cloud-api-restore-endpoint.md | 7 ++----- .../cockroachcloud/managed-backups-advanced.md | 2 +- src/current/cockroachcloud/managed-backups-basic.md | 9 +++------ src/current/cockroachcloud/managed-backups.md | 11 +++-------- 4 files changed, 9 insertions(+), 20 deletions(-) diff --git a/src/current/_includes/cockroachcloud/backups/cloud-api-restore-endpoint.md b/src/current/_includes/cockroachcloud/backups/cloud-api-restore-endpoint.md index 0a853afefc1..15c6e1918ef 100644 --- a/src/current/_includes/cockroachcloud/backups/cloud-api-restore-endpoint.md +++ b/src/current/_includes/cockroachcloud/backups/cloud-api-restore-endpoint.md @@ -5,7 +5,7 @@ You can use the `/v1/clusters/{destination_cluster_id}/restores` endpoint to res {% if page.name == "managed-backups-advanced.md" %} On Advanced clusters, restore operations can be performed at the cluster, database, or table level into the same cluster or a different Advanced cluster in the same organization. {% else %} -On Standard and Basic clusters, restore operations can only be performed into the same cluster where the managed backup is stored. Managed backups can only be restored at the cluster level. +On Standard and Basic clusters, managed backups can only be restored at the cluster level into the same cluster or a different cluster of the same plan type in the same organization. {% endif %} #### Restore a cluster @@ -40,8 +40,7 @@ curl --request POST \ }' ~~~ -{% if page.name == "managed-backups-advanced.md" %} -To restore a cluster backup into a different cluster, ensure that the destination cluster is created and contains no databases/schemas/tables. Send the restore request to the destination cluster ID, specifying the ID of the source cluster as `source_cluster_id`. Both the source cluster and the destination cluster must use the Advanced plan. +To restore a cluster backup into a different cluster, ensure that the destination cluster is created with the same plan type ({{ site.data.products.basic }}, {{ site.data.products.standard }}, or {{ site.data.products.advanced }}) and contains no databases/schemas/tables. Send the restore request to the destination cluster ID, specifying the ID of the source cluster as `source_cluster_id`. {% include_cached copy-clipboard.html %} ~~~ shell @@ -56,8 +55,6 @@ curl --request POST \ You can specify additional options for the restore job in the `restore_opts` object. For more information, see the [API endpoint documentation](https://www.cockroachlabs.com/docs/api/cloud/v1#get-/api/v1/clusters/-cluster_id-/restores-config). -{% endif %} - If the request is successful, the client recieves a JSON response that describes the request operation: ~~~ json diff --git a/src/current/cockroachcloud/managed-backups-advanced.md b/src/current/cockroachcloud/managed-backups-advanced.md index cb0e449d2dd..07c8502b8f6 100644 --- a/src/current/cockroachcloud/managed-backups-advanced.md +++ b/src/current/cockroachcloud/managed-backups-advanced.md @@ -58,7 +58,7 @@ You can set your retention duration **once**. After you have adjusted the retent ## Considerations - Every backup will be stored entirely in a single region, which is chosen at random from the list of cluster regions at the time of cluster creation. This region will be used indefinitely to store backups. -- You can perform a cross-cluster restore across {{ site.data.products.advanced }} clusters that belong to the same organization. However, this cross-cluster restore is not supported for {{ site.data.products.standard }} and {{ site.data.products.basic }} clusters. +- You can perform a cross-cluster restore across clusters in the same organization. However, the target cluster must also be an {{ site.data.products.advanced }} cluster and be completely wiped of data. - You cannot restore a backup of a multi-region database into a single-region database. - For details on managed backups and enabling CMEK in {{ site.data.products.advanced }} clusters, refer to [Backup and restore operations on a cluster with CMEK]({% link cockroachcloud/cmek.md %}#backup-and-restore-operations-on-a-cluster-with-cmek). diff --git a/src/current/cockroachcloud/managed-backups-basic.md b/src/current/cockroachcloud/managed-backups-basic.md index ce718bd0ae8..e6d76bc0289 100644 --- a/src/current/cockroachcloud/managed-backups-basic.md +++ b/src/current/cockroachcloud/managed-backups-basic.md @@ -29,6 +29,7 @@ For details on viewing and managing the backups, refer to the [Cloud Console](#r ## Considerations - Every backup will be stored entirely in a single region, which is chosen at random from the list of cluster regions at the time of cluster creation. This region will be used indefinitely to store backups. +- You can perform a cross-cluster restore across clusters in the same organization. However, the target cluster must also be a {{ site.data.products.basic }} cluster and be completely wiped of data. {% include cockroachcloud/backups/costs-link.md %} @@ -66,13 +67,9 @@ To restore a cluster: The **Restore cluster** module displays with backup details. -1. You can restore a backup to the same cluster. +1. You can restore a backup to the same cluster or a different {{ site.data.products.basic }} cluster. The target cluster must already be created. Select the desired target cluster under **Restore to cluster** and click **Continue** - {{site.data.alerts.callout_info}} - If you need to restore data into a new or different cluster, use [self-managed backups]({% link cockroachcloud/take-and-restore-self-managed-backups.md %}) or [contact support]({% link {{site.current_cloud_version}}/support-resources.md %}). - {{site.data.alerts.end}} - -1. Click **Restore**. +1. Review the restore details then click **Restore**. ## Cloud API diff --git a/src/current/cockroachcloud/managed-backups.md b/src/current/cockroachcloud/managed-backups.md index 4ecd7cb215e..35fcd38bd4f 100644 --- a/src/current/cockroachcloud/managed-backups.md +++ b/src/current/cockroachcloud/managed-backups.md @@ -62,9 +62,8 @@ You can set your retention duration **once**. After you have adjusted the retent ## Considerations - Every backup will be stored entirely in a single region, which is chosen at random from the list of cluster regions at the time of cluster creation. This region will be used indefinitely to store backups. -- You can perform a cross-cluster restore across {{ site.data.products.advanced }} clusters that belong to the same organization. However, this cross-cluster restore is not supported for {{ site.data.products.standard }} and {{ site.data.products.basic }} clusters. +- You can perform a cross-cluster restore across clusters in the same organization. However, the target cluster must also be a {{ site.data.products.standard }} cluster and be completely wiped of data. - You cannot restore a backup of a multi-region database into a single-region database. -- For details on managed backups and enabling CMEK in {{ site.data.products.advanced }} clusters, refer to [Backup and restore operations on a cluster with CMEK]({% link cockroachcloud/cmek.md %}#backup-and-restore-operations-on-a-cluster-with-cmek). ### Required permissions to restore managed backups @@ -120,13 +119,9 @@ To restore a cluster: The **Restore cluster** module displays with backup details. -1. You can restore a backup to the same cluster. +1. You can restore a backup to the same cluster or a different {{ site.data.products.standard }} cluster. The target cluster must already be created. Select the desired target cluster under **Restore to cluster** and click **Continue** - {{site.data.alerts.callout_info}} - If you need to restore data into a new or different cluster, use [self-managed backups]({% link cockroachcloud/take-and-restore-self-managed-backups.md %}) or [contact support]({% link {{site.current_cloud_version}}/support-resources.md %}). - {{site.data.alerts.end}} - -1. Click **Restore**. +1. Review the restore details then click **Restore**. ## Cloud API