Description of problem:
A number of customers have had various issues with their databases where it is no longer consistent with the state of their configuration. The causes are diverse and include bugs, environmental integrity, and inadvertent damage caused by the user. This often results in extensive, complex, and long lasting support efforts to repair. This is an RFE to address some of these issues.

Solutions might include
* Corruption checking at the database page level
    Possible support in PostgreSQL 9.3 and later
* Data consistency checking within the engine database
    Are all the relationships between data objects intact?
    Do the relationships make sense?
* Sync the database based on querying the hosts via vdsm
    Compare data objects in the database against the actual
    data obtained from running hypervisors via vdsm

Version-Release number of selected component (if applicable):
RHEV-M 3.4.z is the current release.

How reproducible:
Happens for various reasons and there is no single useful reproducer.

Expected results:
Numerous database problems should be detectable and reported accurately.
Some database problems should be automatically corrected based on the actual state of the configuration.

Additional info: