Studying Time: 2 mins

The file-level backup function presented in vCSA 6.5 could be very powerfull and schedulable (beginning with vCSA 6.7) as a result of every so often the image-level backup won’t give you the correct integrity when you have corrupted recordsdata throughout the VM.

Additionally with vSphere 7.0 is imaginable tracking the standing of the file-level backup without delay from vSphere Shopper and that is reasonably usefull to have this knowledge direct visual from the UI:

However with model 7.0 Replace 3 one thing works in a different way and your scheduled backup might fail.

If in case you have set the DB Well being Take a look at possibility, all backup will fail.

DB Well being Take a look at is helping you resolve the standing of your database. Backup will take longer if the DB well being take a look at is enabled. Longer time, however you might be reasonably positive that the DB is restorable!

From the backup activity process listing, you are going to discovered the rationale of the failure.

The message recommended: “Db well being is UNHEALTHY, Backup Failed.Disable well being take a look at to take backup in present state.”

VMware has already documented this factor in KB 86084 (VAMI backups fail with Db well being is UNHEALTHY, Backup Failed. Disable well being take a look at to take backup in present state).

It is a identified factor on vCenter 7.0 U3!

There was alternate in DB schema which isn’t refreshed submit patching and therefore when its checking the DB schema it’s failing. Unchecking it, is not going to purpose any impact. Operating the command discussed underneath will refresh the most recent DB schema and the validation would be successful.

The answer is simply run, from the vCSA shell, this command:

 /usr/bin/dbcc -fbss embedded

Then restart your backup