HP Instant Capacity Version 10.x User Guide (762794-002, June 2014)

NOTE: It is advisable not to downgrade the iCAP version. If done so, GiCAP database version
does not change.
The following error message can be seen, while executing the icapmanage command: "This
version of iCAP does not support version X database”.
To resolve this issue, update the iCAP version and recreate the GiCAP setup.
If you restore an OS image for the active Group Manager, the latest GiCAP database might get
overwritten with the older one. The overwrite operation might also occur on the standby Group
Manager with the periodical GiCAP database transfer.
To avoid such accidental overwrite operations, you might consider making the standby Group
Manager the active Group Manager with the command icapmanage -Q. If you do not want to
execute icapmanage -Q on the standby Group Manager or configure a standby Group Manager,
it would be a good idea to have a copy of the latest GiCAP database on any server at all times.
To recover the latest GiCAP database on the active Group Manager after the OS restore operation,
perform the following operation :
# cimprovider -dm HP_GiCAPProviderModule
# scp -p root@<SGM or anywhere>:<...>/GiCAP_db.latest
/etc/opt/iCAP/GiCAP_db
# cimprovider -em HP_GiCAPProviderModule
NOTE: Starting from B.11.31.10.09.00.01 version, database updates sent from Active GM to
Standy GM are stored on the disk in two files.
• /etc/opt/iCAP/GiCAP_db_update
• etc/opt/iCAP/GiCAP_rules_update
The transfer of update is triggered in multiple ways including execution of icapmanage or
icapmodify command, which update the database on the Active GM or icapmanage -t to
transfer the database explicitly to Standy GM. The files are deleted from the disk when the
icapmanage command is run on the Standby GM and the latest update is processed by the
Standyby GM.
84 GiCAP