Detecting MongoDB resources

Edit online

After you add your MongoDB application servers to IBM Storage® Protect Plus, an inventory is run automatically to detect all MongoDB instances and databases. You can run a manual inventory on any application server to detect, list, and store all MongoDB databases for the selected host.

Before you begin

Ensure that you added your MongoDB application servers to IBM Storage Protect Plus. For instructions, see Adding a MongoDB application server.

Important:

Enable IP hostname resolution for all replica set member hosts on any MongoDB server that is registered in IBM Storage Protect Plus. When a MongoDB replica set member IP address is not able to be resolved to a hostname, the inventory will then use the IP address as the key property for the clusterHosts property which includes dots. Cataloging of the database instance fails on inventory with the following error message: 

Cataloging failed for server <servername>:
org.springframework.data.mapping.model.MappingException: 
Map key <hostname> contains dots but no replacement was configured! 
Make sure map keys don't contain dots in the first place or configure an appropriate replacement!

Procedure

  1. In the navigation panel, expand Manage Protection > Databases > MongoDB.
    Tip: To add more MongoDB instances to the Instances pane, follow the instructions in Adding a MongoDB application server.
  2. Click Run Inventory.

    When the inventory is running, the button changes to Inventory In Progress. You can run an inventory on any available application servers, but you can run only one inventory process at a time.

    To monitor the inventory job, go to Jobs and Operations. Click the Running Jobs tab, and look for the latest Application Server Inventory log entry.

    Completed jobs are shown on the Job History tab. You can use the Sort By list to sort jobs based on start time, type, status, job name, or duration. Use the Search by name field to search for jobs by name. You can use asterisks as wildcard characters in the name.

  3. Click an instance to open a view that shows the databases that are detected for that instance. If any databases are missing from the Instances list, check your MongoDB application server and rerun the inventory. In some cases, certain databases are marked as ineligible for backup; hover over the database to reveal the reason why.
    Tip: To return to the list of instances, click the Instances link in the Backup MongoDB pane.
    Attention: If you register more than one application server for one replica set, the instance name that is displayed might change after each inventory, backup, or restore operation. The host name of the most recently inventoried application server that belongs to the replica set is used as part of the instance name. An inventory operation is run as part of backup and restore operations.

What to do next

To start protecting MongoDB databases that are cataloged in the selected instance, apply a service level agreement (SLA) policy to the instance. For instructions about setting an SLA policy, see Defining an SLA policy.