Removal of Active Failover (#377)

* Remove AF content from 3.12 except drivers and integrations

* Deprecation warning in 3.11, upgrading to cluster

Author: Simran-B

site/content/3.11/deploy/active-failover/_index.md

@@ -18,6 +18,11 @@ An _Active Failover_ is defined as:
 An _Active Failover_ behaves differently from an [ArangoDB Cluster](../cluster/_index.md),
 please see the [limitations section](#limitations) for more details.
 
+{{< warning >}}
+The Active Failover deployment mode is deprecated and will no longer be
+supported in the next minor version of ArangoDB, from v3.12 onward.
+{{< /warning >}}
+
 ![ArangoDB Active Failover](../../../images/leader-follower.png)
 
 The advantage of the _Active Failover_ setup is that there is an active third party, the _Agency_,

site/content/3.11/operations/upgrading/manual-deployments/active-failover.md

@@ -19,6 +19,11 @@ to a new hotfix version, or to perform an upgrade to a new minor version of Aran
 Please refer to the [Upgrade paths](../_index.md#upgrade-paths) section
 for detailed information.
 
+{{< warning >}}
+The Active Failover deployment mode is deprecated and will no longer be
+supported in the next minor version of ArangoDB, from v3.12 onward.
+{{< /warning >}}
+
 ## Preparations
 
 The ArangoDB installation packages (e.g. for Debian or Ubuntu) set up a

site/content/3.11/release-notes/version-3.11/incompatible-changes-in-3-11.md

@@ -7,6 +7,12 @@ description: >-
   this ArangoDB version and adjust any client applications if necessary
 archetype: default
 ---
+## Active Failover deployment mode deprecation
+
+Running a single server with asynchronous replication to one or more passive
+single servers for automatic failover is deprecated and will no longer be
+supported in the next minor version of ArangoDB, from v3.12 onward.
+
 ## Extended naming constraints for collections, Views, and indexes
 
 In ArangoDB 3.9, the `--database.extended-names-databases` startup option was

site/content/3.12/about-arangodb/features/_index.md

@@ -75,9 +75,7 @@ See all [Enterprise Edition Features](enterprise-edition.md).
 
 You can install ArangoDB on your local machine or run it in a Docker container
 for development purposes. You can deploy it on-premises as a
-[single server](../../deploy/single-instance/_index.md), optionally
-as a resilient pair with asynchronous replication and automatic failover
-([Active Failover](../../deploy/active-failover/_index.md)),
+[single server](../../deploy/single-instance/_index.md)
 or as a [cluster](../../deploy/cluster/_index.md)
 comprised of multiple nodes with synchronous replication and automatic failover
 for high availability and resilience. For the highest level of data safety,

site/content/3.12/about-arangodb/features/community-edition.md

@@ -67,10 +67,6 @@ see [arangodb.com/community-server/](https://www.arangodb.com/community-server/)
   is reached. Synchronous replication works on a per-shard basis. For each
   collection, you can configure how many copies of each shard are kept in the cluster.
 
-- [**Active Failover**](../../deploy/active-failover/_index.md):
-  Run a single server with asynchronous replication to one or more passive
-  single servers for automatic failover.
-
 - [**Automatic Failover Cluster**](../../deploy/cluster/_index.md#automatic-failover):
   If a nodes goes down, another node takes over to avoid any downtime. <!-- TODO: Can we say that? -->
 

site/content/3.12/components/tools/arangobackup/_index.md

@@ -23,7 +23,7 @@ Hot backups rely on hard link magic performed on the database's
 persistence layer.
 
 _arangobackup_ can be used for all ArangoDB deployment modes
-(Single Instance, Active Failover, Cluster). It always creates what
+(Single Instance, Cluster). It always creates what
 is most readily described as a persistence layer consistent snapshot
 of the entire instance. Therefore, no such thing as database or
 collection level hot backup exists. Consequently, unlike with

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

@@ -45,10 +45,9 @@ arangod --version
 
 ## Starter deployment modes
 
-The Starter supports 3 different modes of ArangoDB deployments:
+The Starter supports different modes of ArangoDB deployments:
 
 1. Single server
-1. Active failover
 1. Cluster
 
 Note: Datacenter replication is an option for the `cluster` deployment mode.
@@ -153,11 +152,10 @@ Running the Starter with the configuration example above and adding the
 
 ## Running on multiple machines
 
-For the `activefailover` and `cluster` mode, it is required to run multiple
-Starters, as every Starter only launches a subset of all servers needed
-to form the entire deployment.
-In the `cluster` mode, for example, a single Starter launches at most one Agent,
-one DB-Server, and one Coordinator.
+For the `cluster` mode, it is required to run multiple Starters, as every Starter
+only launches a subset of all servers needed to form the entire deployment.
+For example, a single Starter launches at most one Agent, one DB-Server, and one
+Coordinator.
 
 It is the responsibility of the user to run the Starter on multiple machines such
 that enough servers are started to form the entire deployment.
@@ -191,8 +189,8 @@ The `setup.json` config file must not be edited manually.
 
 ## Running on multiple machines (under the hood)
 
-As mentioned above, when the Starter is used to create an `activefailover`
-or `cluster` deployment, it first creates a "cluster" of Starters.
+As mentioned above, when the Starter is used to create a or `cluster` deployment,
+it first creates a "cluster" of Starters.
 
 These are the steps taken by the Starters to bootstrap such a deployment
 from scratch.

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

@@ -42,12 +42,11 @@ for details.
 Start a local (test) cluster. Since all servers are running on a single machine
 this is really not intended for production setups.
 
-- `--starter.mode=cluster|single|activefailover`
+- `--starter.mode=cluster|single`
 
 Select what kind of database configuration you want.
-This can be a `cluster` configuration (which is the default),
-a `single` server configuration or a `activefailover` configuration with
-2 single services configured to take over when needed.
+This can be a `cluster` configuration (which is the default) or a
+`single` server configuration.
 
 Note that when running a `single` server configuration you lose all
 high availability features that a cluster provides you.

site/content/3.12/components/tools/arangodump/_index.md

@@ -14,7 +14,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
+Cluster, and DC2DC) 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/3.12/components/tools/arangodump/limitations.md

@@ -12,6 +12,5 @@ _arangodump_ has the following limitations:
   [Hot Backups](../../../operations/backup-and-restore.md#hot-backups) for an alternative). It is
   therefore recommended not to  perform any data-modification operations on the
   cluster while _arangodump_ is running. This is in contrast to what happens on
-  a single instance or an active failover setup, where even if
-  write operations are ongoing, the created dump is consistent, as a snapshot
-  is taken when the dump starts.
+  a single instance, where even if write operations are ongoing, the created dump
+  is consistent, as a snapshot is taken when the dump starts.