Troubleshooting DB2 setup problems

Setting up a backup server for multiple production systems in a DB2® HADR environment

If you use one backup system for multiple production systems, you must use different profiles for each of those production systems. The self-signed certificates must be copied from the primary server to each production system. This setup enables the mount agent to connect to each production system. Every production system in the setup must use the same self-signed certificate.

Problem

The backup system has a DB2 instance with the same name as the DB2 instance on the production systems, including the same instance home directory, and user ID. When you set up a IBM Storage Protect Snapshot backup system with the DB2 setup script on the secondary DB2 server, the backup system configuration for the primary DB2 server is overwritten. The profile on the backup server points to the acsd on the primary DB2 server. For this reason, it cannot connect because the IBM Storage Protect Snapshot primary DB2 server uses different self-signed certificates than the secondary DB2 server.

Solution

To use the same backup system for the primary and secondary node in a DB2 HADR environment, you must start the mount agent twice with different IBM Storage Protect Snapshot profiles, one for every production system. Each production system must use the same self-signed certificate. For the steps required, see Setting up a backup server for multiple production systems in a DB2 HADR environment.