Document the unbind-system-db command and add details about the system db in cluster

modules/ROOT/content-nav.adoc

@@ -160,6 +160,7 @@
 ** xref:clustering/servers.adoc[]
 ** xref:clustering/unbind.adoc[]
 ** xref:clustering/databases.adoc[]
+** xref:clustering/unbind-system-database.adoc[]
 ** Monitoring
 *** xref:clustering/monitoring/show-servers-monitoring.adoc[]
 *** xref:clustering/monitoring/show-databases-monitoring.adoc[]

modules/ROOT/pages/clustering/databases.adoc

@@ -9,6 +9,23 @@ To specify the initial topology, use the command `CREATE DATABASE`.
 To change the topology once the database is created, run the `ALTER DATABASE` command.
 If a database is no longer needed, the command `DROP DATABASE` deletes the database from the cluster.
 
+[[cluster-system-db]]
+== The `system` database in a cluster
+
+The `system` database contains metadata on the DBMS and security configuration.
+When connected to this database you can only perform a specific set of administrative tasks, such as managing databases, servers, and access control.
+
+In the clustered environment, the `system` database can be in a primary or secondary mode.
+To configure its mode, use the xref:configuration/configuration-settings.adoc#config_server.cluster.system_database_mode[`server.cluster.system_database_mode`] setting.
+
+Deploying a cluster for the first time, consider configuring the xref:configuration/configuration-settings.adoc#config_dbms.cluster.minimum_initial_system_primaries_count[`dbms.cluster.minimum_initial_system_primaries_count`].
+This setting defaults to `3`.
+See xref:clustering/setup/deploy.adoc[] for details.
+
+For information on how to recover the `system` database, refer to the xref:clustering/multi-region-deployment/disaster-recovery.adoc#make-the-system-database-write-available[Disaster recovery guide -> Make the `system` database write-available].
+
+
+
 [[create-database]]
 == `CREATE DATABASE`
 

modules/ROOT/pages/clustering/unbind-system-database.adoc

@@ -0,0 +1,77 @@
+:description: The page describes the neo4j-admin command `dbms unbind-system-db`.
+[role=enterprise-edition]
+
+= Unbind the `system` database
+
+You can use the `neo4j-admin dbms unbind-system-db` command to remove and archive the cluster state for the `system` database, so that the server can rebind to a new `system` database in the cluster.
+
+[[unbind-system-db-syntax]]
+== Syntax
+
+The `neo4j-admin dbms unbind-system-db` command has the following syntax:
+
+----
+neo4j-admin dbms unbind-system-db [-h] [--expand-commands] [--verbose] [--archive-cluster-state[=true|false]]
+                                  [--additional-config=<file>] [--archive-path=<path>]
+----
+
+
+[[unbind-system-db-description]]
+== Description
+
+Removes and archives cluster state for `system` database.
+
+[[unbind-system-db-options]]
+== Options
+
+
+The `neo4j-admin dbms unbind-system-db` command has the following options:
+
+.`neo4j-admin dbms unbind-system-db` options
+[options="header", cols="5m,6a,2m"]
+|===
+| Option
+| Description
+| Default
+
+|--additional-config=<file>
+|Configuration file with additional configuration.
+|
+
+|--archive-cluster-state[=true\|false]
+|Enable or disable the cluster state archiving.
+|false
+
+|--archive-path=<path>
+|Destination (file or folder) of the cluster state archive.
+|
+
+|--expand-commands
+|Allow command expansion in config value evaluation.
+|
+
+|-h, --help
+|Show this help message and exit.
+|
+
+|--verbose
+|Enable verbose output.
+|
+|===
+
+[[unbind-system-db-limitations]]
+== Limitations
+
+The Neo4j process must be shut down on all servers before running the `neo4j-admin dbms unbind-system-db` command.
+
+[[unbind-system-db-usage]]
+== Usage
+
+The `neo4j-admin dbms unbind-system-db` command removes and archives cluster state for the `system` database, so that the server can rebind to a new `system` database in a cluster.
+
+This command should be run on all remaining members on a cluster to work as expected. Furthermore, the Neo4j process must be shut down before the command is issued.
+For details, see xref:clustering/multi-region-deployment/disaster-recovery.adoc#make-the-system-database-write-available[Disaster recovery guide -> Make the `system` database write-available].
+
+This does not affect the other databases cluster state.
+However, since all servers in the DBMS need to be shut down when the command is issued, downtime is expected for all databases inside of the DBMS.
+

modules/ROOT/pages/database-administration/index.adoc

@@ -83,6 +83,8 @@ image::manage-dbs-community.svg[title="A default Neo4j installation.",role=popup
 .An installation of Neo4j with multiple active databases, named `marketing`, `sales`, and `hr`:
 image::manage-dbs-enterprise.svg[title="A multiple database Neo4j installation.",role=popup]
 
+For details about the `system` database in a clustered environment, refer to the xref:clustering/databases.adoc#cluster-system-db[Managing databases in a cluster -> The `system` database]. 
+
 == Composite databases
 
 A Composite database is a logical grouping of multiple graphs contained in other, standard databases.

modules/ROOT/pages/neo4j-admin-neo4j-cli.adoc

@@ -59,6 +59,7 @@ For details, see xref:configuration/set-initial-password.adoc[Set an initial pas
 
 | `unbind-system-db`
 | Removes and archives the cluster state of the `system` database so the instance can rebind to a new cluster state of the `system` database.
+For details, see xref:clustering/unbind-system-database.adoc[].
 
 .13+| `server`