diff --git a/src/current/v23.2/physical-cluster-replication-overview.md b/src/current/v23.2/physical-cluster-replication-overview.md index e156f029509..52308c0f3dc 100644 --- a/src/current/v23.2/physical-cluster-replication-overview.md +++ b/src/current/v23.2/physical-cluster-replication-overview.md @@ -9,8 +9,6 @@ docs_area: manage {% include feature-phases/preview.md %} Refer to the [Known Limitations](#known-limitations) section for further detail. - -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. {{site.data.alerts.end}} {% include_cached new-in.html version="v23.2" %} CockroachDB **physical cluster replication (PCR)** continuously sends all data at the cluster level from a _primary_ cluster to an independent _standby_ cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster. diff --git a/src/current/v24.1/physical-cluster-replication-overview.md b/src/current/v24.1/physical-cluster-replication-overview.md index a48965727f2..468d1b504c6 100644 --- a/src/current/v24.1/physical-cluster-replication-overview.md +++ b/src/current/v24.1/physical-cluster-replication-overview.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - CockroachDB **physical cluster replication (PCR)** continuously sends all data at the cluster level from a _primary_ cluster to an independent _standby_ cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster. You can [_cut over_]({% link {{ page.version.version }}/cutover-replication.md %}) from the primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time (in the past or future) where all ingested data is consistent, and make the standby ready to accept application traffic. diff --git a/src/current/v24.2/physical-cluster-replication-overview.md b/src/current/v24.2/physical-cluster-replication-overview.md index 896644747cf..0f4406e7e0b 100644 --- a/src/current/v24.2/physical-cluster-replication-overview.md +++ b/src/current/v24.2/physical-cluster-replication-overview.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - CockroachDB **physical cluster replication (PCR)** continuously sends all data at the cluster level from a _primary_ cluster to an independent _standby_ cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster. You can [_cut over_]({% link {{ page.version.version }}/cutover-replication.md %}) from the primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time (in the past or future) where all ingested data is consistent, and make the standby ready to accept application traffic. diff --git a/src/current/v24.3/create-virtual-cluster.md b/src/current/v24.3/create-virtual-cluster.md index 87b2178c750..994eb925fe4 100644 --- a/src/current/v24.3/create-virtual-cluster.md +++ b/src/current/v24.3/create-virtual-cluster.md @@ -13,10 +13,6 @@ The `CREATE VIRTUAL CLUSTER` statement creates a new virtual cluster. It is supp {% include {{ page.version.version }}/physical-replication/phys-rep-sql-pages.md %} -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - ## Required privileges `CREATE VIRTUAL CLUSTER` requires one of the following privileges: diff --git a/src/current/v24.3/drop-virtual-cluster.md b/src/current/v24.3/drop-virtual-cluster.md index bc83ffe95c1..5806940be39 100644 --- a/src/current/v24.3/drop-virtual-cluster.md +++ b/src/current/v24.3/drop-virtual-cluster.md @@ -7,8 +7,6 @@ docs_area: reference.sql {{site.data.alerts.callout_info}} {% include feature-phases/preview.md %} - -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. {{site.data.alerts.end}} The `DROP VIRTUAL CLUSTER` statement removes virtual clusters in order to restart a **physical cluster replication (PCR)** stream. Virtual clusters are used only as part of the [PCR]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) workflow. diff --git a/src/current/v24.3/physical-cluster-replication-monitoring.md b/src/current/v24.3/physical-cluster-replication-monitoring.md index 429baddd24f..755f166ea80 100644 --- a/src/current/v24.3/physical-cluster-replication-monitoring.md +++ b/src/current/v24.3/physical-cluster-replication-monitoring.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - You can monitor a [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) stream using: - [`SHOW VIRTUAL CLUSTER ... WITH REPLICATION STATUS`](#sql-shell) in the SQL shell. diff --git a/src/current/v24.3/physical-cluster-replication-overview.md b/src/current/v24.3/physical-cluster-replication-overview.md index cf29b69296a..135b5abef5c 100644 --- a/src/current/v24.3/physical-cluster-replication-overview.md +++ b/src/current/v24.3/physical-cluster-replication-overview.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - CockroachDB **physical cluster replication (PCR)** continuously sends all data at the cluster level from a _primary_ cluster to an independent _standby_ cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster. You can [_fail over_]({% link {{ page.version.version }}/failover-replication.md %}) from the primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time (in the past or future) where all ingested data is consistent, and make the standby ready to accept application traffic. diff --git a/src/current/v24.3/physical-cluster-replication-technical-overview.md b/src/current/v24.3/physical-cluster-replication-technical-overview.md index ed961976c99..0eb5c70c931 100644 --- a/src/current/v24.3/physical-cluster-replication-technical-overview.md +++ b/src/current/v24.3/physical-cluster-replication-technical-overview.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - [**Physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) automatically and continuously streams data from an active _primary_ CockroachDB cluster to a passive _standby_ cluster. Each cluster contains: a _system virtual cluster_ and an application [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}): {% include {{ page.version.version }}/physical-replication/interface-virtual-cluster.md %} diff --git a/src/current/v24.3/set-up-physical-cluster-replication.md b/src/current/v24.3/set-up-physical-cluster-replication.md index cfaa3dfdd7b..c039e3dc30a 100644 --- a/src/current/v24.3/set-up-physical-cluster-replication.md +++ b/src/current/v24.3/set-up-physical-cluster-replication.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - In this tutorial, you will set up [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) between a primary cluster and standby cluster. The primary cluster is _active_, serving application traffic. The standby cluster is _passive_, accepting updates from the primary cluster. The replication stream will send changes from the primary to the standby. The unit of replication is a [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}), which is part of the underlying infrastructure in the primary and standby clusters. diff --git a/src/current/v25.1/create-virtual-cluster.md b/src/current/v25.1/create-virtual-cluster.md index 183f02d732d..1e50c80e74d 100644 --- a/src/current/v25.1/create-virtual-cluster.md +++ b/src/current/v25.1/create-virtual-cluster.md @@ -13,10 +13,6 @@ The `CREATE VIRTUAL CLUSTER` statement creates a new virtual cluster. It is supp {% include {{ page.version.version }}/physical-replication/phys-rep-sql-pages.md %} -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - ## Required privileges `CREATE VIRTUAL CLUSTER` requires one of the following privileges: diff --git a/src/current/v25.1/drop-virtual-cluster.md b/src/current/v25.1/drop-virtual-cluster.md index bc83ffe95c1..5806940be39 100644 --- a/src/current/v25.1/drop-virtual-cluster.md +++ b/src/current/v25.1/drop-virtual-cluster.md @@ -7,8 +7,6 @@ docs_area: reference.sql {{site.data.alerts.callout_info}} {% include feature-phases/preview.md %} - -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. {{site.data.alerts.end}} The `DROP VIRTUAL CLUSTER` statement removes virtual clusters in order to restart a **physical cluster replication (PCR)** stream. Virtual clusters are used only as part of the [PCR]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) workflow. diff --git a/src/current/v25.1/physical-cluster-replication-monitoring.md b/src/current/v25.1/physical-cluster-replication-monitoring.md index 429baddd24f..755f166ea80 100644 --- a/src/current/v25.1/physical-cluster-replication-monitoring.md +++ b/src/current/v25.1/physical-cluster-replication-monitoring.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - You can monitor a [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) stream using: - [`SHOW VIRTUAL CLUSTER ... WITH REPLICATION STATUS`](#sql-shell) in the SQL shell. diff --git a/src/current/v25.1/physical-cluster-replication-overview.md b/src/current/v25.1/physical-cluster-replication-overview.md index c9387f1bb20..b66b219c1c8 100644 --- a/src/current/v25.1/physical-cluster-replication-overview.md +++ b/src/current/v25.1/physical-cluster-replication-overview.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - CockroachDB **physical cluster replication (PCR)** continuously sends all data at the cluster level from a _primary_ cluster to an independent _standby_ cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster. You can [_fail over_]({% link {{ page.version.version }}/failover-replication.md %}) from the primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time (in the past or future) where all ingested data is consistent, and make the standby ready to accept application traffic. diff --git a/src/current/v25.1/physical-cluster-replication-technical-overview.md b/src/current/v25.1/physical-cluster-replication-technical-overview.md index 53318a8ffa3..837e8ef6ac8 100644 --- a/src/current/v25.1/physical-cluster-replication-technical-overview.md +++ b/src/current/v25.1/physical-cluster-replication-technical-overview.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - [**Physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) automatically and continuously streams data from an active _primary_ CockroachDB cluster to a passive _standby_ cluster. Each cluster contains: a _system virtual cluster_ and an application [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}) during the PCR stream: {% include {{ page.version.version }}/physical-replication/interface-virtual-cluster.md %} diff --git a/src/current/v25.1/set-up-physical-cluster-replication.md b/src/current/v25.1/set-up-physical-cluster-replication.md index 15c90098d9c..7e2e7191f9a 100644 --- a/src/current/v25.1/set-up-physical-cluster-replication.md +++ b/src/current/v25.1/set-up-physical-cluster-replication.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - In this tutorial, you will set up [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) between a primary cluster and standby cluster. The primary cluster is _active_, serving application traffic. The standby cluster is _passive_, accepting updates from the primary cluster. The replication stream will send changes from the primary to the standby. The unit of replication is a [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}), which is part of the underlying infrastructure in the primary and standby clusters. diff --git a/src/current/v25.2/create-virtual-cluster.md b/src/current/v25.2/create-virtual-cluster.md index bb3d38cb582..137367a88d3 100644 --- a/src/current/v25.2/create-virtual-cluster.md +++ b/src/current/v25.2/create-virtual-cluster.md @@ -13,10 +13,6 @@ The `CREATE VIRTUAL CLUSTER` statement creates a new virtual cluster. It is supp {% include {{ page.version.version }}/physical-replication/phys-rep-sql-pages.md %} -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - ## Required privileges {% include_cached new-in.html version="v25.2" %} The following [privileges]({% link {{ page.version.version }}/security-reference/authorization.md %}#supported-privileges) are required to start a PCR stream with `CREATE VIRTUAL CLUSTER`: diff --git a/src/current/v25.2/drop-virtual-cluster.md b/src/current/v25.2/drop-virtual-cluster.md index 203f6e0ec8b..f472ef0456c 100644 --- a/src/current/v25.2/drop-virtual-cluster.md +++ b/src/current/v25.2/drop-virtual-cluster.md @@ -7,8 +7,6 @@ docs_area: reference.sql {{site.data.alerts.callout_info}} {% include feature-phases/preview.md %} - -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. {{site.data.alerts.end}} The `DROP VIRTUAL CLUSTER` statement removes virtual clusters in order to restart a **physical cluster replication (PCR)** stream. Virtual clusters are used only as part of the [PCR]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) workflow. diff --git a/src/current/v25.2/physical-cluster-replication-monitoring.md b/src/current/v25.2/physical-cluster-replication-monitoring.md index 429baddd24f..755f166ea80 100644 --- a/src/current/v25.2/physical-cluster-replication-monitoring.md +++ b/src/current/v25.2/physical-cluster-replication-monitoring.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - You can monitor a [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) stream using: - [`SHOW VIRTUAL CLUSTER ... WITH REPLICATION STATUS`](#sql-shell) in the SQL shell. diff --git a/src/current/v25.2/physical-cluster-replication-overview.md b/src/current/v25.2/physical-cluster-replication-overview.md index c9387f1bb20..b66b219c1c8 100644 --- a/src/current/v25.2/physical-cluster-replication-overview.md +++ b/src/current/v25.2/physical-cluster-replication-overview.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - CockroachDB **physical cluster replication (PCR)** continuously sends all data at the cluster level from a _primary_ cluster to an independent _standby_ cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster. You can [_fail over_]({% link {{ page.version.version }}/failover-replication.md %}) from the primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time (in the past or future) where all ingested data is consistent, and make the standby ready to accept application traffic. diff --git a/src/current/v25.2/physical-cluster-replication-technical-overview.md b/src/current/v25.2/physical-cluster-replication-technical-overview.md index 64ab3a24fb9..83b4c3d30a9 100644 --- a/src/current/v25.2/physical-cluster-replication-technical-overview.md +++ b/src/current/v25.2/physical-cluster-replication-technical-overview.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - [**Physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) automatically and continuously streams data from an active _primary_ CockroachDB cluster to a passive _standby_ cluster. Each cluster contains: a _system virtual cluster_ and an application [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}) during the PCR stream: {% include {{ page.version.version }}/physical-replication/interface-virtual-cluster.md %} diff --git a/src/current/v25.2/set-up-physical-cluster-replication.md b/src/current/v25.2/set-up-physical-cluster-replication.md index 85230e9eddd..b69c3752065 100644 --- a/src/current/v25.2/set-up-physical-cluster-replication.md +++ b/src/current/v25.2/set-up-physical-cluster-replication.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - In this tutorial, you will set up [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) between a primary cluster and standby cluster. The primary cluster is _active_, serving application traffic. The standby cluster is _passive_, accepting updates from the primary cluster. The replication stream will send changes from the primary to the standby. The unit of replication is a [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}), which is part of the underlying infrastructure in the primary and standby clusters. diff --git a/src/current/v25.3/create-virtual-cluster.md b/src/current/v25.3/create-virtual-cluster.md index fb2c9d32f9e..c1ca09b2200 100644 --- a/src/current/v25.3/create-virtual-cluster.md +++ b/src/current/v25.3/create-virtual-cluster.md @@ -13,10 +13,6 @@ The `CREATE VIRTUAL CLUSTER` statement creates a new virtual cluster. It is supp {% include {{ page.version.version }}/physical-replication/phys-rep-sql-pages.md %} -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - ## Required privileges The following [privileges]({% link {{ page.version.version }}/security-reference/authorization.md %}#supported-privileges) are required to start a PCR stream with `CREATE VIRTUAL CLUSTER`: diff --git a/src/current/v25.3/drop-virtual-cluster.md b/src/current/v25.3/drop-virtual-cluster.md index 203f6e0ec8b..f472ef0456c 100644 --- a/src/current/v25.3/drop-virtual-cluster.md +++ b/src/current/v25.3/drop-virtual-cluster.md @@ -7,8 +7,6 @@ docs_area: reference.sql {{site.data.alerts.callout_info}} {% include feature-phases/preview.md %} - -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. {{site.data.alerts.end}} The `DROP VIRTUAL CLUSTER` statement removes virtual clusters in order to restart a **physical cluster replication (PCR)** stream. Virtual clusters are used only as part of the [PCR]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) workflow. diff --git a/src/current/v25.3/physical-cluster-replication-monitoring.md b/src/current/v25.3/physical-cluster-replication-monitoring.md index 429baddd24f..755f166ea80 100644 --- a/src/current/v25.3/physical-cluster-replication-monitoring.md +++ b/src/current/v25.3/physical-cluster-replication-monitoring.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - You can monitor a [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) stream using: - [`SHOW VIRTUAL CLUSTER ... WITH REPLICATION STATUS`](#sql-shell) in the SQL shell. diff --git a/src/current/v25.3/physical-cluster-replication-overview.md b/src/current/v25.3/physical-cluster-replication-overview.md index c9387f1bb20..b66b219c1c8 100644 --- a/src/current/v25.3/physical-cluster-replication-overview.md +++ b/src/current/v25.3/physical-cluster-replication-overview.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - CockroachDB **physical cluster replication (PCR)** continuously sends all data at the cluster level from a _primary_ cluster to an independent _standby_ cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster. You can [_fail over_]({% link {{ page.version.version }}/failover-replication.md %}) from the primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time (in the past or future) where all ingested data is consistent, and make the standby ready to accept application traffic. diff --git a/src/current/v25.3/physical-cluster-replication-technical-overview.md b/src/current/v25.3/physical-cluster-replication-technical-overview.md index d9f93168d50..92cc10332a5 100644 --- a/src/current/v25.3/physical-cluster-replication-technical-overview.md +++ b/src/current/v25.3/physical-cluster-replication-technical-overview.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - [**Physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) automatically and continuously streams data from an active _primary_ CockroachDB cluster to a passive _standby_ cluster. Each cluster contains: a _system virtual cluster_ and an application [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}) during the PCR stream: {% include {{ page.version.version }}/physical-replication/interface-virtual-cluster.md %} diff --git a/src/current/v25.3/set-up-physical-cluster-replication.md b/src/current/v25.3/set-up-physical-cluster-replication.md index 85230e9eddd..b69c3752065 100644 --- a/src/current/v25.3/set-up-physical-cluster-replication.md +++ b/src/current/v25.3/set-up-physical-cluster-replication.md @@ -5,10 +5,6 @@ toc: true docs_area: manage --- -{{site.data.alerts.callout_info}} -Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters. -{{site.data.alerts.end}} - In this tutorial, you will set up [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) between a primary cluster and standby cluster. The primary cluster is _active_, serving application traffic. The standby cluster is _passive_, accepting updates from the primary cluster. The replication stream will send changes from the primary to the standby. The unit of replication is a [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}), which is part of the underlying infrastructure in the primary and standby clusters.