Skip to main content
A newer release of this product is available.

Restoring the Admin Node database when recovering a non-primary Admin Node

Contributors
PDFs

If you want to retain the historical information about attributes, alarms, and alerts on a non-primary Admin Node that has failed, you can restore the Admin Node database from the primary Admin Node.

  • The recovered Admin Node must be installed and running.

  • The StorageGRID system must include at least two Admin Nodes.

  • You must have the Passwords.txt file.

  • You must have the provisioning passphrase.

If an Admin Node fails, the historical information stored in its Admin Node database is lost. This database includes the following information:

  • Alert history

  • Alarm history

  • Historical attribute data, which is used in the charts and text reports available from the Support > Tools > Grid Topology page.

When you recover an Admin Node, the software installation process creates an empty Admin Node database on the recovered node. However, the new database only includes information for servers and services that are currently part of the system or added later.

If you restored a non-primary Admin Node, you can restore the historical information by copying the Admin Node database from the primary Admin Node (the source Admin Node) to the recovered node.

Note Copying the Admin Node database might take several hours. Some Grid Manager features will be unavailable while services are stopped on the source node.

  1. Log in to the source 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 from the source Admin Node. Then, enter the provisioning passphrase if prompted. recover-access-points

  3. From the source Admin Node, stop the MI service: service mi stop

  4. From the source Admin Node, stop the Management Application Program Interface (mgmt-api) service: service mgmt-api stop

  5. Complete the following steps on the recovered Admin Node:

    1. Log in to the recovered 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. Stop the mgmt-api service: service mgmt-api stop

    4. Add the SSH private key to the SSH agent. Enter:ssh-add

    5. Enter the SSH Access Password listed in the Passwords.txt file.

    6. Copy the database from the source Admin Node to the recovered Admin Node: /usr/local/mi/bin/mi-clone-db.sh Source_Admin_Node_IP

    7. When prompted, confirm that you want to overwrite the MI database on the recovered Admin Node.

      The database and its historical data are copied to the recovered Admin Node. When the copy operation is done, the script starts the recovered Admin Node.

    8. When you no longer require passwordless access to other servers, remove the private key from the SSH agent. Enter:ssh-add -D

  6. Restart the services on the source Admin Node: service servermanager start