Previous Next JavaScript must be enabled to correctly display this content

## Create an Administration Process on a Specific Storage Node

Every data store has an administration database. The Admin CLI is currently connected to the Storage Node `node01`. Use the `deploy-sn` command to deploy the Storage Node `node01`. You then use the command `deploy-admin` to deploy an Administration process on the same Storage Node `node01` to continue configuring this data store.

The `deploy-admin` command creates an Administration process, with the same type as the Storage Node (SN) zone — if the zone is primary, the Admin is a primary Admin; if a secondary zone, so is the Admin.

Secondary Admins support failover. If a primary Admin fails, it converts to an offline secondary to re-establish quorum using existing Admins. A secondary Admin converts to a primary to take over for the failed primary. For more information on how quorum is applied, see the Concepts Guide.

To support failover, ensure that any zones used to continue data store operation after a failure contain at least one Admin node.

Note:

A deployed Admin must be the same type (`PRIMARY` or `SECONDARY`) as its zone. Also, the number of deployed Admins in a zone should be equal to the Zone Replication Factor.

The `deploy-sn` command requires a Zone ID. You can get this ID by using the `show topology` command:

    kv-> show topology

Output:

    store=mystore  numPartitions=0 sequence=1
    zn: id=zn1 name=Boston repFactor=1 type=PRIMARY
    allowArbiters=false masterAffinity=false

The zone ID is `zn1` in the output.

When you deploy the Storage Node, provide the zone ID, the node's network name, and its registry port number. For example:

    kv-> plan deploy-sn -zn zn1 -host <hostname> -port 5000 -wait

Output:

    Executed plan 2, waiting for completion...
    Plan 2 ended successfully

Having deployed the Storage Node, create the Admin process on the Storage Node that you just deployed, using the `deploy-admin` command. This command requires the Storage Node ID (which you can obtain using the `show topology` command) and an optional plan name.

    kv-> plan deploy-admin -sn sn1 -wait

Output:

    Executed plan 3, waiting for completion...
    Plan 3 ended successfully