The BIRT iHub administrator uses third-party RDBMS tools to manage the backup, recovery, and failover capabilities of the cluster and volume metadata database. The administrator uses standard operating system or other third‑party tools to manage the backup and recovery of the data files.

The third-party database schemas that contain cluster and volume metadata are critical components of a BIRT iHub system. To guard against data loss, the database administrator must back up the cluster and volume schemas and all related file data to ensure recoverability in the event of failure. Please consult Actuate Support at the time of installation if you have any questions about the backup, recovery, or failover procedures necessary to protect a BIRT iHub system against the possibility of catastrophic failure.

For more information on backing up an BIRT iHub installation, see Backing up BIRT iHub System.

In BIRT iHub, there is no concept of volume failover, since each node in a cluster can operate on all the volumes. Configuring cluster and volume database failover is the responsibility of the third-party RDBMS administrator. The database administrator must use the facilities available in the RDBMS to configure this failover capability. Consult the third-party RDBMS documentation for detailed information on how to use native system tools to configure backup, recovery, and failover operations for the externally managed cluster and volume database.

Documentation for a PostgreSQL RDBMS is available at:

Documentation for an Oracle RDBMS is available at: