You can configure one or more vCenter Hyperic databases, including implementing optional properties.

The retention strategy that vCenter Hyperic uses for measurement data is it to store the minimum amount of data required to pinpoint when changes in performance or availability occur.

A secondary database instance is configured to store detailed measurement data replicated from the primary vCenter Hyperic database.

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

If you use the built-in vCenter Hyperic database, you must back it up.

In addition to backing up the vCenter Hyperic database, you might want to back up other files in your server directory.

vCenter Hyperic server stores monitoring results using a tiered model to minimize the volume of data stored, while still providing sufficient data granularity. Periodically, the vCenter Hyperic server removes detailed metric data from the database and archives it.

vCenter Hyperic administrators can view real-time vCenter Hyperic server and database health and load data by clicking HQ Health on the Administration page in the vCenter Hyperic user interface.

The key vCenter Hyperic database tables include information about resources, metric collection, and measurements.

Here is a list of the key resources and measurement table structure for the vCenter Hyperic database.

Here are examples of regular maintenance for MySQL