Skip to content

Commit 5d00a4d

Browse files
committed
Remove disaster recovery BU/Restore sections from preview CV docs
1 parent 06e006d commit 5d00a4d

10 files changed

+0
-266
lines changed

Diff for: src/current/v23.2/cluster-virtualization-overview.md

-14
Original file line numberDiff line numberDiff line change
@@ -52,20 +52,6 @@ To upgrade to a new major version when cluster virtualization is enabled, you mu
5252

5353
For details, refer to [Work with virtual clusters]({% link {{ page.version.version }}/work-with-virtual-clusters.md %}#upgrade-a-cluster).
5454

55-
### Disaster recovery
56-
57-
When cluster virtualization is enabled, [backup]({% link {{ page.version.version }}/backup.md %}) and [restore]({% link {{ page.version.version }}/restore.md %}) commands are scoped to a virtual cluster. This means that:
58-
59-
- A backup taken from a virtual cluster contains all data for that virtual cluster, but does not contain modifications made via the system virtual cluster such as system-level cluster settings.
60-
- If your deployment contains system-level customizations, you can take a separate backup of the system virtual cluster to capture them.
61-
- A backup of a virtual cluster can be restored as a virtual cluster in any CockroachDB cluster with cluster virtualization enabled.
62-
63-
For more details about backing up and restoring a cluster with cluster virtualization enabled, refer to [Work with virtual clusters]({% link {{ page.version.version }}/work-with-virtual-clusters.md %}#disaster-recovery).
64-
65-
{{site.data.alerts.callout_success}}
66-
For details about configuring and using PCR for disaster recovery, refer to [Physical Cluster Replication Overview]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}).
67-
{{site.data.alerts.end}}
68-
6955
### Observability
7056

7157
When cluster virtualization is enabled, cluster log messages and metrics are scoped to a virtual cluster or to the system virtual cluster, and are labeled with the name of the virtual cluster they relate to.

Diff for: src/current/v23.2/work-with-virtual-clusters.md

-40
Original file line numberDiff line numberDiff line change
@@ -121,46 +121,6 @@ When connected to a virtual cluster from the DB Console:
121121

122122
- Some pages and views are by default viewable only from the system virtual cluster, including those pertaining to overall cluster health.
123123

124-
## Disaster recovery
125-
126-
When cluster virtualization is enabled, [backup]({% link {{ page.version.version }}/backup.md %}) and [restore]({% link {{ page.version.version }}/restore.md %}) commands are scoped to the virtual cluster by default.
127-
128-
### Back up a virtual cluster
129-
130-
To back up a virtual cluster:
131-
132-
1. [Connect to the virtual cluster](#connect-to-a-virtual-cluster) you want to back up as a user with the `admin` role on the virtual cluster.
133-
1. [Back up the cluster]({% link {{ page.version.version }}/backup.md %}). Only the virtual cluster's data and settings are included in the backup, and data and settings for other virtual clusters or for the system virtual cluster is omitted.
134-
135-
For details about restoring a backup of a virtual cluster, refer to [Restore a virtual cluster](#restore-a-virtual-cluster).
136-
137-
### Back up the entire cluster
138-
139-
To back up the entire CockroachDB cluster, including all virtual clusters and the system virtual cluster:
140-
141-
1. [Connect to the system virtual cluster](#connect-to-the-system-virtual-cluster) as a user with the `admin` role on the system virtual cluster.
142-
1. [Back up the cluster]({% link {{ page.version.version }}/backup.md %}), and include the `INCLUDE_ALL_SECONDARY_TENANTS` flag in the `BACKUP` command. All virtual clusters and the system virtual cluster are included in the backup.
143-
144-
### Restore a virtual cluster
145-
146-
You can restore a backup of a virtual cluster to:
147-
148-
- The original virtual cluster on the original CockroachDB cluster.
149-
- A different virtual cluster on the original CockroachDB cluster.
150-
- A different virtual cluster on a different CockroachDB cluster with cluster virtualization enabled.
151-
152-
To restore only a virtual cluster:
153-
154-
1. [Connect to the destination virtual cluster](#connect-to-a-virtual-cluster) as a user with the `admin` role on the virtual cluster.
155-
1. [Restore the cluster]({% link {{ page.version.version }}/restore.md %}). Only the virtual cluster's data and settings are restored.
156-
157-
### Restore the entire cluster
158-
159-
To restore the entire CockroachDB cluster, including all virtual clusters and the system virtual cluster:
160-
161-
1. [Connect to the destination system virtual cluster](#connect-to-the-system-virtual-cluster) as a user with the `admin` role on the system virtual cluster.
162-
1. [Restore the cluster]({% link {{ page.version.version }}/restore.md %}) from a backup that included the the `INCLUDE_ALL_SECONDARY_VIRTUAL_CLUSTERS` flag. All virtual clusters and the system virtual cluster are restored.
163-
164124
## Configure cluster settings
165125

166126
When [cluster virtualization]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}) is enabled, each [cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}) is scoped to either a virtual cluster or the system virtual cluster.

Diff for: src/current/v24.1/cluster-virtualization-overview.md

-13
Original file line numberDiff line numberDiff line change
@@ -52,19 +52,6 @@ To upgrade to a new major version when cluster virtualization is enabled, you mu
5252

5353
For details, refer to [Work with virtual clusters]({% link {{ page.version.version }}/work-with-virtual-clusters.md %}#upgrade-a-cluster).
5454

55-
### Disaster recovery
56-
57-
When cluster virtualization is enabled, [backup]({% link {{ page.version.version }}/backup.md %}) and [restore]({% link {{ page.version.version }}/restore.md %}) commands are scoped to a virtual cluster. This means that:
58-
59-
- A backup taken from a virtual cluster contains all data for that virtual cluster, but does not contain modifications made via the system virtual cluster such as system-level cluster settings.
60-
- If your deployment contains system-level customizations, you can take a separate backup of the system virtual cluster to capture them.
61-
- A backup of a virtual cluster can be restored as a virtual cluster in any CockroachDB cluster with cluster virtualization enabled.
62-
63-
For more details about backing up and restoring a cluster with cluster virtualization enabled, refer to [Work with virtual clusters]({% link {{ page.version.version }}/work-with-virtual-clusters.md %}#disaster-recovery).
64-
65-
{{site.data.alerts.callout_success}}
66-
For details about configuring and using PCR for disaster recovery, refer to [Physical Cluster Replication Overview]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}).
67-
{{site.data.alerts.end}}
6855

6956
### Observability
7057

Diff for: src/current/v24.1/work-with-virtual-clusters.md

-40
Original file line numberDiff line numberDiff line change
@@ -114,46 +114,6 @@ sql_txn_commit_count{tenant="demo"} 0
114114

115115
When connected to a virtual cluster from the DB Console, metrics which measure SQL and related activity show data scoped to the virtual cluster. All other metrics are collected system-wide and display the same data on all virtual clusters including the system virtual cluster.
116116

117-
## Disaster recovery
118-
119-
When cluster virtualization is enabled, [backup]({% link {{ page.version.version }}/backup.md %}) and [restore]({% link {{ page.version.version }}/restore.md %}) commands are scoped to the virtual cluster by default.
120-
121-
### Back up a virtual cluster
122-
123-
To back up a virtual cluster:
124-
125-
1. [Connect to the virtual cluster](#connect-to-a-virtual-cluster) you want to back up as a user with the `admin` role on the virtual cluster.
126-
1. [Back up the cluster]({% link {{ page.version.version }}/backup.md %}). Only the virtual cluster's data and settings are included in the backup, and data and settings for other virtual clusters or for the system virtual cluster is omitted.
127-
128-
For details about restoring a backup of a virtual cluster, refer to [Restore a virtual cluster](#restore-a-virtual-cluster).
129-
130-
### Back up the entire cluster
131-
132-
To back up the entire CockroachDB cluster, including all virtual clusters and the system virtual cluster:
133-
134-
1. [Connect to the system virtual cluster](#connect-to-the-system-virtual-cluster) as a user with the `admin` role on the system virtual cluster.
135-
1. [Back up the cluster]({% link {{ page.version.version }}/backup.md %}), and include the `INCLUDE_ALL_SECONDARY_TENANTS` flag in the `BACKUP` command. All virtual clusters and the system virtual cluster are included in the backup.
136-
137-
### Restore a virtual cluster
138-
139-
You can restore a backup of a virtual cluster to:
140-
141-
- The original virtual cluster on the original CockroachDB cluster.
142-
- A different virtual cluster on the original CockroachDB cluster.
143-
- A different virtual cluster on a different CockroachDB cluster with cluster virtualization enabled.
144-
145-
To restore only a virtual cluster:
146-
147-
1. [Connect to the destination virtual cluster](#connect-to-a-virtual-cluster) as a user with the `admin` role on the virtual cluster.
148-
1. [Restore the cluster]({% link {{ page.version.version }}/restore.md %}). Only the virtual cluster's data and settings are restored.
149-
150-
### Restore the entire cluster
151-
152-
To restore the entire CockroachDB cluster, including all virtual clusters and the system virtual cluster:
153-
154-
1. [Connect to the destination system virtual cluster](#connect-to-the-system-virtual-cluster) as a user with the `admin` role on the system virtual cluster.
155-
1. [Restore the cluster]({% link {{ page.version.version }}/restore.md %}) from a backup that included the the `INCLUDE_ALL_SECONDARY_VIRTUAL_CLUSTERS` flag. All virtual clusters and the system virtual cluster are restored.
156-
157117
## Configure cluster settings
158118

159119
When [cluster virtualization]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}) is enabled, each [cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}) is scoped to either a virtual cluster or the system virtual cluster.

Diff for: src/current/v24.2/cluster-virtualization-overview.md

-13
Original file line numberDiff line numberDiff line change
@@ -52,19 +52,6 @@ To upgrade to a new major version when cluster virtualization is enabled, you mu
5252

5353
For details, refer to [Work with virtual clusters]({% link {{ page.version.version }}/work-with-virtual-clusters.md %}#upgrade-a-cluster).
5454

55-
### Disaster recovery
56-
57-
When cluster virtualization is enabled, [backup]({% link {{ page.version.version }}/backup.md %}) and [restore]({% link {{ page.version.version }}/restore.md %}) commands are scoped to a virtual cluster. This means that:
58-
59-
- A backup taken from a virtual cluster contains all data for that virtual cluster, but does not contain modifications made via the system virtual cluster such as system-level cluster settings.
60-
- If your deployment contains system-level customizations, you can take a separate backup of the system virtual cluster to capture them.
61-
- A backup of a virtual cluster can be restored as a virtual cluster in any CockroachDB cluster with cluster virtualization enabled.
62-
63-
For more details about backing up and restoring a cluster with cluster virtualization enabled, refer to [Work with virtual clusters]({% link {{ page.version.version }}/work-with-virtual-clusters.md %}#disaster-recovery).
64-
65-
{{site.data.alerts.callout_success}}
66-
For details about configuring and using PCR for disaster recovery, refer to [Physical Cluster Replication Overview]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}).
67-
{{site.data.alerts.end}}
6855

6956
### Observability
7057

Diff for: src/current/v24.2/work-with-virtual-clusters.md

-40
Original file line numberDiff line numberDiff line change
@@ -114,46 +114,6 @@ sql_txn_commit_count{tenant="demo"} 0
114114

115115
When connected to a virtual cluster from the DB Console, metrics which measure SQL and related activity show data scoped to the virtual cluster. All other metrics are collected system-wide and display the same data on all virtual clusters including the system virtual cluster.
116116

117-
## Disaster recovery
118-
119-
When cluster virtualization is enabled, [backup]({% link {{ page.version.version }}/backup.md %}) and [restore]({% link {{ page.version.version }}/restore.md %}) commands are scoped to the virtual cluster by default.
120-
121-
### Back up a virtual cluster
122-
123-
To back up a virtual cluster:
124-
125-
1. [Connect to the virtual cluster](#connect-to-a-virtual-cluster) you want to back up as a user with the `admin` role on the virtual cluster.
126-
1. [Back up the cluster]({% link {{ page.version.version }}/backup.md %}). Only the virtual cluster's data and settings are included in the backup, and data and settings for other virtual clusters or for the system virtual cluster is omitted.
127-
128-
For details about restoring a backup of a virtual cluster, refer to [Restore a virtual cluster](#restore-a-virtual-cluster).
129-
130-
### Back up the entire cluster
131-
132-
To back up the entire CockroachDB cluster, including all virtual clusters and the system virtual cluster:
133-
134-
1. [Connect to the system virtual cluster](#connect-to-the-system-virtual-cluster) as a user with the `admin` role on the system virtual cluster.
135-
1. [Back up the cluster]({% link {{ page.version.version }}/backup.md %}), and include the `INCLUDE_ALL_SECONDARY_TENANTS` flag in the `BACKUP` command. All virtual clusters and the system virtual cluster are included in the backup.
136-
137-
### Restore a virtual cluster
138-
139-
You can restore a backup of a virtual cluster to:
140-
141-
- The original virtual cluster on the original CockroachDB cluster.
142-
- A different virtual cluster on the original CockroachDB cluster.
143-
- A different virtual cluster on a different CockroachDB cluster with cluster virtualization enabled.
144-
145-
To restore only a virtual cluster:
146-
147-
1. [Connect to the destination virtual cluster](#connect-to-a-virtual-cluster) as a user with the `admin` role on the virtual cluster.
148-
1. [Restore the cluster]({% link {{ page.version.version }}/restore.md %}). Only the virtual cluster's data and settings are restored.
149-
150-
### Restore the entire cluster
151-
152-
To restore the entire CockroachDB cluster, including all virtual clusters and the system virtual cluster:
153-
154-
1. [Connect to the destination system virtual cluster](#connect-to-the-system-virtual-cluster) as a user with the `admin` role on the system virtual cluster.
155-
1. [Restore the cluster]({% link {{ page.version.version }}/restore.md %}) from a backup that included the the `INCLUDE_ALL_SECONDARY_VIRTUAL_CLUSTERS` flag. All virtual clusters and the system virtual cluster are restored.
156-
157117
## Configure cluster settings
158118

159119
When [cluster virtualization]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}) is enabled, each [cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}) is scoped to either a virtual cluster or the system virtual cluster.

Diff for: src/current/v24.3/cluster-virtualization-overview.md

-13
Original file line numberDiff line numberDiff line change
@@ -58,19 +58,6 @@ To upgrade to a new major version when cluster virtualization is enabled, you mu
5858

5959
For details, refer to [Work with virtual clusters]({% link {{ page.version.version }}/work-with-virtual-clusters.md %}#upgrade-a-cluster).
6060

61-
### Disaster recovery
62-
63-
When cluster virtualization is enabled, [backup]({% link {{ page.version.version }}/backup.md %}) and [restore]({% link {{ page.version.version }}/restore.md %}) commands are scoped to a virtual cluster. This means that:
64-
65-
- A backup taken from a virtual cluster contains all data for that virtual cluster, but does not contain modifications made via the system virtual cluster such as system-level cluster settings.
66-
- If your deployment contains system-level customizations, you can take a separate backup of the system virtual cluster to capture them.
67-
- A backup of a virtual cluster can be restored as a virtual cluster in any CockroachDB cluster with cluster virtualization enabled.
68-
69-
For more details about backing up and restoring a cluster with cluster virtualization enabled, refer to [Work with virtual clusters]({% link {{ page.version.version }}/work-with-virtual-clusters.md %}#disaster-recovery).
70-
71-
{{site.data.alerts.callout_success}}
72-
For details about configuring and using PCR for disaster recovery, refer to [Physical Cluster Replication Overview]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}).
73-
{{site.data.alerts.end}}
7461

7562
### Observability
7663

Diff for: src/current/v24.3/work-with-virtual-clusters.md

-40
Original file line numberDiff line numberDiff line change
@@ -114,46 +114,6 @@ sql_txn_commit_count{tenant="demo"} 0
114114

115115
When connected to a virtual cluster from the DB Console, metrics which measure SQL and related activity show data scoped to the virtual cluster. All other metrics are collected system-wide and display the same data on all virtual clusters including the system virtual cluster.
116116

117-
## Disaster recovery
118-
119-
When cluster virtualization is enabled, [backup]({% link {{ page.version.version }}/backup.md %}) and [restore]({% link {{ page.version.version }}/restore.md %}) commands are scoped to the virtual cluster by default.
120-
121-
### Back up a virtual cluster
122-
123-
To back up a virtual cluster:
124-
125-
1. [Connect to the virtual cluster](#connect-to-a-virtual-cluster) you want to back up as a user with the `admin` role on the virtual cluster.
126-
1. [Back up the cluster]({% link {{ page.version.version }}/backup.md %}). Only the virtual cluster's data and settings are included in the backup, and data and settings for other virtual clusters or for the system virtual cluster is omitted.
127-
128-
For details about restoring a backup of a virtual cluster, refer to [Restore a virtual cluster](#restore-a-virtual-cluster).
129-
130-
### Back up the entire cluster
131-
132-
To back up the entire CockroachDB cluster, including all virtual clusters and the system virtual cluster:
133-
134-
1. [Connect to the system virtual cluster](#connect-to-the-system-virtual-cluster) as a user with the `admin` role on the system virtual cluster.
135-
1. [Back up the cluster]({% link {{ page.version.version }}/backup.md %}), and include the `INCLUDE_ALL_SECONDARY_TENANTS` flag in the `BACKUP` command. All virtual clusters and the system virtual cluster are included in the backup.
136-
137-
### Restore a virtual cluster
138-
139-
You can restore a backup of a virtual cluster to:
140-
141-
- The original virtual cluster on the original CockroachDB cluster.
142-
- A different virtual cluster on the original CockroachDB cluster.
143-
- A different virtual cluster on a different CockroachDB cluster with cluster virtualization enabled.
144-
145-
To restore only a virtual cluster:
146-
147-
1. [Connect to the destination virtual cluster](#connect-to-a-virtual-cluster) as a user with the `admin` role on the virtual cluster.
148-
1. [Restore the cluster]({% link {{ page.version.version }}/restore.md %}). Only the virtual cluster's data and settings are restored.
149-
150-
### Restore the entire cluster
151-
152-
To restore the entire CockroachDB cluster, including all virtual clusters and the system virtual cluster:
153-
154-
1. [Connect to the destination system virtual cluster](#connect-to-the-system-virtual-cluster) as a user with the `admin` role on the system virtual cluster.
155-
1. [Restore the cluster]({% link {{ page.version.version }}/restore.md %}) from a backup that included the the `INCLUDE_ALL_SECONDARY_VIRTUAL_CLUSTERS` flag. All virtual clusters and the system virtual cluster are restored.
156-
157117
## Configure cluster settings
158118

159119
When [cluster virtualization]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}) is enabled, each [cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}) is scoped to either a virtual cluster or the system virtual cluster.

Diff for: src/current/v25.1/cluster-virtualization-overview.md

-13
Original file line numberDiff line numberDiff line change
@@ -58,19 +58,6 @@ To upgrade to a new major version when cluster virtualization is enabled, you mu
5858

5959
For details, refer to [Work with virtual clusters]({% link {{ page.version.version }}/work-with-virtual-clusters.md %}#upgrade-a-cluster).
6060

61-
### Disaster recovery
62-
63-
When cluster virtualization is enabled, [backup]({% link {{ page.version.version }}/backup.md %}) and [restore]({% link {{ page.version.version }}/restore.md %}) commands are scoped to a virtual cluster. This means that:
64-
65-
- A backup taken from a virtual cluster contains all data for that virtual cluster, but does not contain modifications made via the system virtual cluster such as system-level cluster settings.
66-
- If your deployment contains system-level customizations, you can take a separate backup of the system virtual cluster to capture them.
67-
- A backup of a virtual cluster can be restored as a virtual cluster in any CockroachDB cluster with cluster virtualization enabled.
68-
69-
For more details about backing up and restoring a cluster with cluster virtualization enabled, refer to [Work with virtual clusters]({% link {{ page.version.version }}/work-with-virtual-clusters.md %}#disaster-recovery).
70-
71-
{{site.data.alerts.callout_success}}
72-
For details about configuring and using PCR for disaster recovery, refer to [Physical Cluster Replication Overview]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}).
73-
{{site.data.alerts.end}}
7461

7562
### Observability
7663

0 commit comments

Comments
 (0)