Restoring the Admin Node database when recovering a primary Admin Node

If you want to retain the historical information about attribute values and alarms on a primary Admin Node that has failed, you need to restore the Admin Node database. This database can only be restored if your StorageGRID Webscale system includes more than one Admin Node.

Before you begin

The recovered Admin Node must be installed and running.
The StorageGRID Webscale system must include one or more Admin Nodes.
You must have the Passwords.txt file.
You must have the provisioning passphrase.

About this task

If an Admin Node fails, the historical information about attribute values and alarms that are stored in its Admin Node database are lost. When you recover an Admin Node, the software installation process creates a new database for the NMS service. After the recovered Admin Node is started, it records attribute and audit information for all services as if you had performed a new installation of the StorageGRID Webscale system.

If you restored a primary Admin Node and your StorageGRID Webscale system has another Admin Node, you can restore this historical information by copying the Admin Node database from a non-primary Admin Node (the source node) to the recovered primary Admin Node. If your system has only a primary Admin Node, you cannot restore the Admin Node database.

Note: Copying the Admin Node database may take several hours. Some Grid Management Interface features will be unavailable while services are stopped on the source Admin Node.

Steps

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.
From the source Admin Node, stop the MI service: /etc/init.d/mi stop
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: /etc/init.d/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 recovered 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 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. 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
Restart the MI service on the source Admin Node./etc/init.d/mi start