When running InfiniGuard version 3.3.x and above,  the  InfiniGuard services include the ability for Backup Admins to use the CLI-based “iguard_db2” tool to review logs and images in protection as well as to transfer logs and images.

This feature allows DBAs access to validate or collect/transfer DB2 data InfiniGuard DDE NetBoost Shares. The tool allows for various scenarios of DB2 Logs and Data on the DDE shares.

Your TA can assist you in obtaining these tools before they are officially available from the Infinidat Support site. Once you have obtained it, it can then be installed (as an RPM) on any AIX 7.1, AIX 7.2, Redhat or Centos Linux server.

Once installed, the script-based tool allows authenticated access to any 3.3.x or above InfiniGuard version to list and get DB2 content from any of the Deduplication Engine NetBoost Shares. The tool requires a read-only account on the InfiniGuard UI (as a minimum).

  1. Install the InfiniGuard_db2 RPM on the system you wish to use as a cli tool server, to validate networking on InfiniGuard Deduplication Engines (DDEs).
  2. Obtain the RPM appropriate for your host operating system (LINUX/AIX) from Infinidat Support or your TA.
  3. Install the RPM using “rpm –ivh INFINIDAT_InfiniGuard_db2.rpm

Once installed, you can use the tool to run cli-based DB2 data queries and get operations.

If issues are discovered, the customer team can work with their DB2 admin staff and/or Infinidat Support to resolve any issues (thru the normal ticket-based support system). Some examples follow.

$ iguard_db2 --help
iguard_db2: Enables to list DB2 logs/images and retrieve DB2 logs located on InfiniGuard system.


  iguard_db2 -c <config> [-a <alias>] [-i <instance>] images
  iguard_db2 -c <config> -a <alias> [-i <instance>] [-n <node>] logs
  iguard_db2 -c <config> -a <alias> [-i <instance>] [-n <node>] get <name> [--path <path>]
  iguard_db2 -c <config> -a <alias> [-i <instance>] [-n <node>] mget <start> <end> [--path <path>]
  iguard_db2 --help

  images                     list backup images
  logs                       list backup logs
  get <name>                 retrieve log file with specific name
  mget <start> <end>         retrieve log sequence from start to end

  -c <config>, --config <config>           config file path
  -a <alias>, --alias <alias>              database alias
  -i <instance>, --instance <instance>     database instance
  -n <node>, --nodenum <node>              node number [default: 0]
  -p <path>, --path <path>                 log files retrieval location [default: ./]
  -h, --help                               show this help

Examples provided below

---images list----------

$ iguard_db2 -c db2.conf images
db2inst2/RRR      20200818140821
db2inst1/A13281   20200818140157
db2inst1/A13281   20200818140140
db2inst1/B13746   20200818140821
db2inst1/A10613   20200818140228
db2inst1/A10613   20200818140212
db2inst1/A10613   20200818140325

----logs list----------
  • Note - logs are listed with a prepended C00000* code on the DDE Shares.
$ iguard_db2 -c db2.conf -a B13746 logs

-----get single log----
  • Note – When the logs are collected for transfer the C000000* code is striped.
$ iguard_db2 -c db2.conf -a B13746 get C0000003_S0000059.LOG
S0000059.LOG wrote 4104192 bytes

------ get multiple logs----

$ iguard_db2 -c db2.conf -a B13746 mget 57 62
S0000057.LOG wrote 12288 bytes
S0000058.LOG wrote 12288 bytes
S0000059.LOG wrote 4104192 bytes
S0000060.LOG wrote 4104192 bytes
S0000061.LOG wrote 4104192 bytes
S0000062.LOG wrote 4104192 bytes
Was this article helpful?
0 out of 0 found this helpful

0 out of 0 found this helpful

Last edited: 2022-08-06 08:20:41 UTC