Reinstalling the config file onto new server and mysql is causing issues

[techK]

Ticket ID: #MOD: Contract ID removed

So long story short, old server hard drives went bad, thankfully had config files backed up. I got a new hard drive in, installed the OS, installed Veeam and loaded up the config file, however near the end of the process, the veeam server backup service doesn't start. Looking at the logs, it says: Login failed for user 'NT AUTHORITY\SYSTEM'. (Veeam.Backup.DBCreator.DatabaseException)

Somehow, the mysql isn't communicating/logging in correctly. I spent a few hours with level 1 support trying to figure this out, their end solution was to uninstall the mysql and reinstall. I'm kind of defeated, two days out of current backups and the anxiety is kind of building. Originally, a 3rd party set up the mysql part of our service, so I'm not even sure if I'm installing the right mysql for my veeam server.

Anyone here got any tips or experience this before? Or maybe a good guide to follow on the reinstall? Thanks in advance for any help.

[Mildur]

Hi techK,

Can you please share the actual case number (#07******)? You’ve shared your contract ID (#03******) instead.

Regarding your question — are you deploying MySQL or MSSQL?
Veeam Backup & Replication supports only Microsoft SQL Server or PostgreSQL Server for its configuration database. Could it be that you’re attempting to use the wrong database engine?

Thank you,
Fabian