MIVB database corruption logs

The MIVB/vMIVB is showing a database corruption alarm and you have decided to perform a backup and restore.

Once it’s completed how do yo know what parts of the DB were corrupt and not restored?

You check this log.

After the controller has come back online and you can log back into it type this command into the maintenace window

TYPE *.DR.logfile_1

In the below example you can see a few extensions that could not be restored due to DB issues

or if you want to follow it while the system is booting

SSH into the MSL and tail the log file

tail -F /var/mivb/active/db/cc/dr/logfile_1.1

or you could just view the file with nano when the process is finished

Hope this helps

Leave a Reply

Your email address will not be published. Required fields are marked *