To perform a complete backup whilst the Broker is shutdown, simply copy all the files the exist beneath \${QPID_WORK}, assuming all virtualhost nodes and virtualhost are in their standard location, this will copy all configuration and persistent message data. There is currently no safe mechanism to take a complete copy of the entire Broker whilst it is running.

To perform a complete backup of a Virtualhost node whilst it is stopped (or Broker down), simply copy all the files the exist beneath \${QPID_WORK}/<nodename>/config, assuming the virtualhost node is in the standard location. This will copy all configuration that belongs to that virtualhost node. The technique for backing up a virtualhost node whilst it is running depends on its type.

BDB module includes the "hot" backup utility org.apache.qpid.server.store.berkeleydb.BDBBackup. This utility can perform the backup when the broker is running. You can run this class from command line like in an example below: java -cp "${QPID_HOME}/lib/*" org.apache.qpid.server.store.berkeleydb.BDBBackup \ -fromdir \${QPID_WORK}/<nodename>/config -todir path/to/backup/folder In the example above BDBBackup utility is called to backup the store at \${QPID_WORK}/<nodename>/config and copy store logs into path/to/backup/folder.

See BDB-HA VirtualHost node backups are node specific. You cannot use the backup of one node to recover a different node. To backup a group a backup of each node needs to be taken separately.

Not yet supported

The responsibility for backup is delegated to the database server itself. See the documentation accompanying it. Any technique that takes a consistent snapshot of the database is acceptable.

JSON stores its config in a single text file. It can be safely backed up using standard command line tools.

To perform a complete backup of a Virtualhost whilst it is stopped (or Broker down), simply copy all the files the exist beneath \${QPID_WORK}/<name>/messages, assuming the virtualhost is in the standard location. This will copy all messages that belongs to that virtualhost. The technique for backing up a virtualhost whilst it is running depends on its type.

Use the same backup utility described above, but use the path \${QPID_WORK}/<name>/messages instead.

Not yet supported

The responsibility for backup is delegated to the database server itself. See the documentation accompanying it. Any technique that takes a consistent snapshot of the database is acceptable.

The contents of the virtualhost will be backed up as part of virtualhost node that contains it.

The contents of the virtualhost will be backed up as part of virtualhost node that contains it.