Managing the HA Data Store

When converting to high-availability operation, you can use the Message Queue Database Manager utility (imqdbmgr) subcommand

   imqdbmgr upgrade hastore

to convert an existing standalone HADB persistent data store to a shared HADB store. You can use this command in the following cases:

• Moving from a Message Queue 4.0 standalone HADB store to a Message Queue 4.1 shared HADB store. In this case, the broker will automatically upgrade the store. You can then run the imqdbmgr upgrade hastore command to convert the upgraded data store for shared use.

• Moving from a standalone Message Queue 4.1 HADB store to a shared HADB store. In this case, you just need to run the imqdbmgr upgrade hastore command to convert the data store for shared use.

Because this command only supports conversion of HADB stores, it cannot be used to convert file-based stores or other JDBC-based stores to a shared HADB store. If you were previously running a 3.x version of Message Queue, you must create an HADB store and then manually migrate your data to that store in order to use the high availability feature.

For durability and reliability, it is a good idea to back up a high-availability cluster’s shared persistent data store periodically to backup files. This creates a snapshot of the data store that you can then use to restore the data in case of catastrophic failure. The command for backing up the data store is

   imqdbmgr backup  -dir backupDir

where backupDir is the path to the directory in which to place the backup files. To restore the data store from these files, use the command

   imqdbmgr restore  -restore backupDir