![]() Now the event log about the database issue makes sense because of the registry setting for the SQL server name. Second go to HKEY_LOCAL_MACHINE > SOFTWARE > Veeam > Veeam Backup Catalog and verify the CatalogSharedFolderPath is correct.Īfter that the service should start up like normal. Apparently sometimes Veeam doesn’t update if you install Veeam before you add the server to the domain.įirst go to HKEY_LOCAL_MACHINE > SOFTWARE > Veeam > Veeam Backup and Replication and verify that SqlServerName is correct and not some random windows generated name. I re-traced the steps I took to configure the server and the last thing I did was add the server to the domain and rebooted.Īfter some web searches I found and option to check the registry. However this was a brand new Veeam server and was using a fresh SQL instance. Veeam wont start and it seemed to be a database issue. The first thing I thought to check was the event logs. Some services stop automatically if they are not in use by other services or programs.’ However, this does not make sense because the main Veeam backup service needs to run. I ran into this issue recently can got the error ‘The Veeam Backup Service service on Local Computer started and then stopped. Have you ever installed a new Veeam Backup server but then Veeam won’t start?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |