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 to retain historical information about attributes, alerts, and alerts.
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 information for servers and services that are currently part of the system or added later. This Admin Node database includes the following information:
- Alert history
- Alarm history
- Historical attribute data, which is used in the charts and text reports available from the page
To ensure that the Admin Node database is consistent between nodes, you can copy the 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 and the Management API service on both the primary Admin Node and the expansion Admin Node before copying the database.