Unbind a Core Server

This section describes how to remove cluster state data from a Neo4j server.

1. Command

The cluster state of a Causal Cluster member can be removed by using the following command:

1.1. Syntax

neo4j-admin unbind [--verbose]

1.2. Options

Option Default Description


Enable verbose output.


Allow command expansion in config value evaluation.



Enable or disable the cluster state archiving.


Destination (file or folder) of the cluster state archive.

1.3. Limitations

The Neo4j server process must be shut down before running the neo4j-admin unbind command.

2. Examples of usage

You can use the neo4j-admin unbind command to:

  • Turn a cluster member into a standalone server:

    To start the Neo4j server in single (standalone) mode after unbinding it from the cluster, first set dbms.mode=SINGLE in neo4j.conf.

  • Seed a Causal Cluster with existing store files:

    To seed a new cluster using the store files of another cluster, you must first run neo4j-admin unbind on each server. For more information about seeding Causal Clusters, see Seed a cluster.

    If a cluster holds a previous version of any of the databases being seeded, you must DROP those databases before seeding. Alternatively, you can stop every instance, unbind them from the cluster using neo4j-admin unbind and then forcefully restore the correct seeds (backups) for the databases in question. If you do not DROP or unbind before seeding, either with neo4j-admin restore or neo4j-admin load, the database’s store files and cluster state will be out of sync, potentially leading to logical corruptions.

  • Recover a Causal Cluster:

    In the event of serious failures you may need to recover an entire Causal Cluster from backups. Before restoring those backups, you must first run neo4j-admin unbind on each server. For more information about recovering databases from online backups, see Restore a database backup.

    From Neo4j version 4.0.0 onwards, you must run the neo4j-admin unbind command on both Read Replicas and Core members.

3. Archive cluster state

To archive the cluster state, from the <neo4j-home> folder, run the neo4j-admin unbind command with the arguments --archive-cluster-state=true and --archive-path=<destination-folder>:

bin/neo4j-admin unbind --archive-path=/path/to/archive-folder --archive-cluster-state=true

The default resultant file is named: