Copying the Admin Node database

When adding Admin Nodes through an expansion procedure, you can optionally copy the database from the primary Admin Node to the new Admin Node. Copying the database allows you retain historical information about attributes.

Before you begin

About this task

The StorageGRID software activation process creates an empty database for the NMS service on the expansion Admin Node. When the NMS service starts on the expansion Admin Node, it records attribute information for servers and services that are currently part of the system or added later. Historical NMS data is not available unless you manually copy the existing database from the primary Admin Node to the expansion Admin Node.

Note: Copying the database from the primary Admin Node (the source Admin Node) to an expansion Admin Node can take up to several hours to complete. During this period, the Grid Manager is inaccessible.

Use these steps to stop the MI service on both the primary Admin Node and the expansion Admin Node before copying the database.

Steps

  1. Complete the following steps on the primary Admin Node:
    1. Log in to the Admin Node:
      1. Enter the following command: ssh admin@grid_node_IP
      2. Enter the password listed in the Passwords.txt file.
      3. Enter the following command to switch to root: su -
      4. Enter the password listed in the Passwords.txt file.
    2. Run the following command: recover-access-points
    3. Enter the provisioning passphrase.
    4. Stop the MI service: service mi stop
  2. Complete the following steps on the expansion Admin Node:
    1. Log in to the expansion Admin Node:
      1. Enter the following command: ssh admin@grid_node_IP
      2. Enter the password listed in the Passwords.txt file.
      3. Enter the following command to switch to root: su -
      4. Enter the password listed in the Passwords.txt file.
    2. Stop the MI service: service mi stop
    3. Add the SSH private key to the SSH agent. Enter:ssh-add
    4. Enter the SSH Access Password listed in the Passwords.txt file.
    5. Copy the database from the source Admin Node to the expansion Admin Node: /usr/local/mi/bin/mi-clone-db.sh Source_Admin_Node_IP
    6. When prompted, confirm that you want to overwrite the MI database on the expansion Admin Node.
      The database and its historical data are copied to the expansion Admin Node. When the copy operation is done, the script starts the expansion Admin Node. The following status appears:

      Database cloned, starting servicesstarting mi ... done

    7. When you no longer require passwordless access to other servers, remove the private key from the SSH agent. Enter:ssh-add -D
  3. Restart the MI service on the source Admin Node.service mi start