Detecting Db2 resources

Edit online

After you add IBM® Db2® application servers to IBM Storage® Protect Plus, an inventory to detect all Db2 instances and databases is run automatically. The inventory detects, lists, and stores all the Db2 databases for the selected host, and makes the databases available for protection with IBM Storage Protect Plus.

Before you begin

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

Important:

Only short hostnames should be used in db2nodes.cfg for Db2. When hosts in the db2nodes.cfg are specified by their fully qualified names, 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!

About this task

Any Db2 partitions that are found in the inventory are listed for the Db2 instance. Partitions are listed by their partition number for each host appended to the host name in the Instances table.

Procedure

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

    When the inventory is running, the button changes to show 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 view the job log, 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 on 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 Db2 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 hypertext in the Backup Db2 pane.

What to do next

To start protecting Db2 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.