The vRealize Hyperic database contains most of the data necessary to recreate your vRealize Hyperic server environment after a failure, or to move the database to a different host.

In addition to historical metrics, the database contains configuration settings, such as vRealize Hyperic agent connection information, collection intervals, portlet configurations, groups, roles, and users. Some server configuration data, such as database connection information, the mail server for alerts, and Java arguments used at server startup, is stored in external files.

Like any other database, your vRealize Hyperic database should be backed up on a regular basis, so that you can restore the data in the event of a failure that corrupts or destroys the database. It is also good practice to backup the database prior to upgrading vRealize Hyperic, your database server, or other software that resides on the server machine.

You should define vRealize Hyperic backup procedures and incorporate them into your overall backup processes. Your local requirements and practices will dictate backup frequency, timing, naming conventions, and retention policies. A daily backup is sufficient for most environments.

Shut Down vRealize Hyperic Server if Backup Makes the Database Unavailable

If your database backup process makes the vRealize Hyperic database unavailable, shut down the vRealize Hyperic server before running the backup.