Testing high availability setup

After you set up the Db2® Data Management Console high availability environment, you can test the setup.

Procedure

  1. Test data sync between online and offline nodes
    1. Update any file in the /Config directory in online node and verify that it is updated to offline node in real time.
    2. Update any file in the /Config directory in offline node and verify that is not updated to online node.
    3. Delete a file in the /Config directory and verify that it is covered from the offline node.
  2. Check that logs folders are periodically synced to offline node.
  3. Manually control failover by using Tivoli® System Automation command. To manually switch control of the Db2 Data Management Console server to be online, ssh to one of the high availability nodes, and run the following commands:
    rgreq -o move dmcrg
    lssam -top    
  4. Recover or start the Db2 Data Management Console node that is online. On the online node, run the stop.sh command to stop the console. Then, run the Tivoli SA MP lssam -top to verify whether Tivoli SA MP tries to turn on Db2 Data Management Console successfully.
  5. Automatic failover.
    1. Restart online node.
    2. Shutdown online node

    In this scenario, when the Db2 Data Management Console server is down, Tivoli SA MP attempts to start the Db2 Data Management Console server a few times. If restart fails, Tivoli SA MP fails over to Db2 Data Management Console on the other node and bring it up.