Remove DC2DC from OEM

Author: Simran-B

site/content/arangodb/3.12/release-notes/version-oem/incompatible-changes-in-oem.md

@@ -53,6 +53,11 @@ deployment offline to perform the upgrade procedure in the safest possible manne
 | 3.11.10 (or older) | 3.11.11 (or newer 3.11.x) | Create a backup, upgrade normally (following the standard [Upgrade path](../../operations/upgrading/_index.md#upgrade-paths) all the way to the latest 3.11.x version), then check for [affected numbers in indexes](#corrected-sorting-order-for-numbers-in-velocypack-indexes) and fix them. |
 | 3.11.11 (or newer 3.11.x) | 3.12.4 (or newer) | **Do not upgrade to version 3.12.0, 3.12.1, 3.12.2, or 3.12.3**. Create a backup, check for [affected numbers in indexes](#corrected-sorting-order-for-numbers-in-velocypack-indexes) and fix them (if you haven't done so already or created the deployment with 3.11.11 or a later 3.11.x version), then upgrade to the latest 3.11.x version first, and finally upgrade to version 3.12.4 or later. |
 
+## Datacenter-to-Datacenter Replication (DC2DC) removed
+
+The _Datacenter-to-Datacenter Replication_ (DC2DC) for clusters including the
+_arangosync_ tool is no longer supported from v3.12 onward.
+
 ## Incompatibilities due to switch to glibc
 
 From version 3.11.10 onward, ArangoDB uses the glibc C standard library

site/content/arangodb/4.0/release-notes/version-oem/incompatible-changes-in-oem.md

@@ -53,6 +53,11 @@ deployment offline to perform the upgrade procedure in the safest possible manne
 | 3.11.10 (or older) | 3.11.11 (or newer 3.11.x) | Create a backup, upgrade normally (following the standard [Upgrade path](../../operations/upgrading/_index.md#upgrade-paths) all the way to the latest 3.11.x version), then check for [affected numbers in indexes](#corrected-sorting-order-for-numbers-in-velocypack-indexes) and fix them. |
 | 3.11.11 (or newer 3.11.x) | 3.12.4 (or newer) | **Do not upgrade to version 3.12.0, 3.12.1, 3.12.2, or 3.12.3**. Create a backup, check for [affected numbers in indexes](#corrected-sorting-order-for-numbers-in-velocypack-indexes) and fix them (if you haven't done so already or created the deployment with 3.11.11 or a later 3.11.x version), then upgrade to the latest 3.11.x version first, and finally upgrade to version 3.12.4 or later. |
 
+## Datacenter-to-Datacenter Replication (DC2DC) removed
+
+The _Datacenter-to-Datacenter Replication_ (DC2DC) for clusters including the
+_arangosync_ tool is no longer supported from v3.12 onward.
+
 ## Incompatibilities due to switch to glibc
 
 From version 3.11.10 onward, ArangoDB uses the glibc C standard library

site/content/arangodb/oem/components/tools/arangobackup/examples.md

@@ -66,8 +66,6 @@ including in the meantime databases, collections, indexes etc.
 The DB-Server of a single server instance and all DB-Servers
 of a cluster will subsequently be restarted.
 
-Datacenter-to-Datacenter Replication (DC2DC) needs to be stopped before
-restoring a Hot Backup.
 {{< /warning >}}
 
 ```bash

site/content/arangodb/oem/components/tools/arangodb-starter/architecture.md

@@ -11,7 +11,7 @@ description: >-
 The ArangoDB Starter is a program used to create ArangoDB database deployments
 on bare-metal (or virtual machines) with ease.
 It enables you to create everything from a simple Single server instance
-to a full blown Cluster with Datacenter-to-Datacenter Replication in under 5 minutes.
+to a full blown Cluster in under 5 minutes.
 
 The Starter is intended to be used in environments where there is no higher
 level orchestration system (e.g. Kubernetes) available.
@@ -50,12 +50,10 @@ The Starter supports 3 different modes of ArangoDB deployments:
 1. Active failover
 1. Cluster
 
-Note: Datacenter replication is an option for the `cluster` deployment mode.
-
 You select one of these modes using the `--starter.mode` command line option.
 
 Depending on the mode you've selected, the Starter launches one or more
-(`arangod` / `arangosync`) server processes.
+`arangod` server processes.
 
 No matter which mode you select, the Starter always provides you
 a common directory structure for storing the servers data, configuration & log files.

site/content/arangodb/oem/components/tools/arangodb-starter/options.md

@@ -189,31 +189,6 @@ command like this:
 arangodb --args.coordinators.log.level=requests=debug
 ```
 
-## Passing through `arangosync` options
-
-Options for `arangosync` that are not supported by the starter can still be
-passed to the syncmasters & syncworkers using a pass through option.
-Every option that start with a pass through prefix is passed through to the
-command-line of one or more `arangosync` instances.
-
-- `--args.sync.<section>.<key>=<value>` is passed as
-  `--<section>.<key>=<value>` to all arangosync instances started by this starter.
-- `--args.syncmasters.<section>.<key>=<value>` is passed as
-  `--<section>.<key>=<value>` to all syncmasters started by this starter.
-- `--args.syncworkers.<section>.<key>=<value>` is passed as
-  `--<section>.<key>=<value>` to all syncworkers started by this starter.
-
-Some options are essential to the function of the starter.
-Therefore these options cannot be passed through like this.
-
-Example:
-
-To set a custom token TTL for direct message queue, use a command like this.
-
-```bash
-arangodb --args.syncmasters.mq.direct-token-ttl=12h ...
-```
-
 ## Passing environment variables
 
 Environment variables by default gonna be passed from arangodb process by
@@ -233,42 +208,6 @@ Example:
 arangodb --envs.all.ARANGODB_OVERRIDE_DETECTED_TOTAL_MEMORY=2G --envs.coordinators.ARANGODB_OVERRIDE_DETECTED_TOTAL_MEMORY=4G --envs.dbservers.ARANGODB_OVERRIDE_DETECTED_TOTAL_MEMORY=8G ...
 ```
 
-## Datacenter-to-Datacenter Replication options
-
-- `--starter.sync=bool`
-
-If set, the Starter also starts `arangosync` instances.
-
-- `--sync.start-master=bool`
-
-Should an ArangoSync master instance be started (only relevant if `--starter.sync`
-is enabled, defaults to `true`)
-
-- `--sync.start-worker=bool`
-
-Should an ArangoSync worker instance be started (only relevant if `--starter.sync`
-is enabled, defaults to `true`)
-
-- `--sync.monitoring.token=<token>`
-
-Bearer token used to access ArangoSync monitoring endpoints.
-
-- `--sync.master.jwt-secret=<secret>`
-
-Path of file containing JWT secret used to access the Sync Master (from Sync Worker).
-
-- `--sync.mq.type=<message queue type>`
-
-Type of message queue used by the Sync Master (defaults to "direct").
-
-- `--sync.server.keyfile=<path of keyfile>`
-
-TLS keyfile of local sync master.
-
-- `--sync.server.client-cafile=<path of CA certificate>`
-
-CA Certificate used for client certificate verification.
-
 ## Miscellaneous options
 
 - `--version`

site/content/arangodb/oem/components/tools/arangodb-starter/security.md

@@ -9,7 +9,7 @@ description: >-
 ## Creating certificates
 
 The starter provides commands to create all certificates needed for an ArangoDB
-deployment with optional Datacenter-to-Datacenter Replication.
+deployment.
 
 ### TLS server certificates
 

site/content/arangodb/oem/components/tools/arangodump/_index.md

@@ -13,7 +13,7 @@ If you want to export for external programs to formats like JSON or CSV, see
 [_arangobackup_](../arangobackup/_index.md).
 
 _arangodump_ can be used for all ArangoDB deployments modes (Single Instance, 
-Active Failover, Cluster and DC2DC) and it can backup selected collections
+Active Failover, and Cluster) and it can backup selected collections
 or all collections of a database, optionally including _system_ collections. One
 can backup the structure, i.e. the collections with their configuration without
 any data, only the data stored in them, or both. If you are using the Enterprise

site/content/arangodb/oem/concepts/data-structure/collections.md

@@ -95,8 +95,7 @@ Please be aware that dumps containing extended names cannot be restored
 into older versions that only support the traditional naming constraints. In a
 cluster setup, it is required to use the same naming constraints for all
 Coordinators and DB-Servers of the cluster. Otherwise, the startup is
-refused. In DC2DC setups, it is also required to use the same naming constraints
-for both datacenters to avoid incompatibilities.
+refused.
 {{< /warning >}}
 
 You can rename collections (except in cluster deployments). This changes the

site/content/arangodb/oem/concepts/data-structure/databases.md

@@ -84,8 +84,7 @@ Please be aware that dumps containing extended names cannot be restored
 into older versions that only support the traditional naming constraints. In a
 cluster setup, it is required to use the same naming constraints for all
 Coordinators and DB-Servers of the cluster. Otherwise, the startup is
-refused. In DC2DC setups it is also required to use the same naming
-constraints for both datacenters to avoid incompatibilities.
+refused.
 {{< /warning >}}
 
 ## Notes

site/content/arangodb/oem/concepts/data-structure/views.md

@@ -93,8 +93,7 @@ Please be aware that dumps containing extended names cannot be restored
 into older versions that only support the traditional naming constraints. In a
 cluster setup, it is required to use the same naming constraints for all
 Coordinators and DB-Servers of the cluster. Otherwise, the startup is
-refused. In DC2DC setups, it is also required to use the same naming constraints
-for both datacenters to avoid incompatibilities.
+refused.
 {{< /warning >}}
 
 You can rename Views (except in cluster deployments). This changes the