Skip to main content

Hi!
We have a Hypervisor server running Windows server 2016. On this we have veeam backup and replication. We had multiple electric outages. UPS damaged and the server received multiple power outages. Fortunately it started, but Veeam does not. It has sql server, but its service with automatic delayed start but is not starting. To manual start still nothing. Event log saying: “the log scan number (5815:437:1) passed to log scan in database ‘master’ is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, recreate the publication. Otherwise, restore from backup if the problem results in a fuilure during startup.”

Seems to me the database damaged. What can I do to fix this? Fix would be preferred if fails how can i create new database to start creating new backups?

Thank you

Peter

Hi @petersonal -

You should be able to do a DB restore to be able to recover Veeam to a workable state. Follow the steps in the User Guide below:

https://helpcenter.veeam.com/docs/backup/vsphere/vbr_config_restore.html?ver=120


If you have a corrupted Veeam database and a good configuration backup then you can recover that way.  If SQL in general as Shane said do a DB restore.


Comment