/Veeam: Backup Service stop working

Veeam: Backup Service stop working

Today after a clean install for a new Veeam Backup Server 9.5 (for testing purposes) in a Windows 2012 R2, when I changed the hostname and added to the Domain, I was not able to login to the Veeam Backup anymore. Checking Backup Service was stopped and cannot restart it again.

Veeam: Backup Service stop working

Veeam: Backup Service stop working

Looking at the Veeam Backup logs ( %allusersprofile%\Veeam\Backup\Svc.VeeamBackup.log ) I see the following entries:

[DB] Disconnecting from SQL Server (ServerInstance=[WIN-05QKKR6UAV9\VEEAMSQL2012])
[DB] Connection is terminated
[DB|ERROR] Unable to connect to SQL Server WIN-05QKKR6UAV9\VEEAMSQL2012. A network-related or instance-specific error occurred while establishing a connection to SQL Server.”

This part is the one I check where was the problem ( [WIN-05QKKR6UAV9\VEEAMSQL2012] ). This was the previous name of this Server. So after I change the name of this Server Veeam Backup installation was still pointing to the previous name. So need to change this entry for the new Server Name.

This needs to be done in the registry in the following entries:

HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\SqlServerName
HKLM\SOFTWARE\Veeam\Veeam Backup Catalog\CatalogSharedFolderPath

Just run the regedit in your Windows Server and change this setting for the new Server name.

Veeam: Backup Service stop working

Veeam: Backup Service stop working

After this, just reboot your server and your Veeam Backup Service will be able to start and you can login to your Veeam Backup console.

Final Notes: If you have a new server to install a new Veeam Backup Server, and then plan to change the Server Name, you should do it before you install Veeam. If you do it after, then you need to follow this procedure to put the Veeam Backup running again.

Hope this information was useful.

Note: Share this article, if you think is worth sharing.

©2017 ProVirtualzone. All Rights Reserved

By | 2018-09-20T18:32:57+02:00 December 22nd, 2016|Backups Posts|2 Comments

About the Author:

I have over 20 years of experience in the IT industry. I have been working with Virtualization for more than 15 years (mainly VMware). I recently obtained certifications, including VCP DCV 2022, VCAP DCV Design 2023, and VCP Cloud 2023. Additionally, I have VCP6.5-DCV, VMware vSAN Specialist, vExpert vSAN, vExpert NSX, vExpert Cloud Provider for the last two years, and vExpert for the last 7 years and a old MCP. My specialties are Virtualization, Storage, and Virtual Backup. I am a Solutions Architect in the area VMware, Cloud and Backup / Storage. I am employed by ITQ, a VMware partner as a Senior Consultant. I am also a blogger and owner of the blog ProVirtualzone.com and recently book author.

2 Comments

  1. Filippo 13/01/2017 at 22:03

    Thank you!

  2. […] have already talked about this issue a couple of years ago in old versions HERE. But now we can fix the problem without touching the regedit with the new Veeam tool […]

Leave A Comment