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.
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.
Use these steps to stop the MI service on both the primary Admin Node and the expansion Admin Node before copying the database.
Database cloned, starting servicesstarting mi ... done