The Backup Exec Device & Media Service does not start after a server name change or a Backup Exec version upgrade.
book
Article ID: 100023022
calendar_today
Updated On:
Resolution
Sometimes, after a version upgrade or a server migration, the services do not start properly and remain starting. The event viewer shows Event Id 33152 errors reporting Adamm Database connection errors (ERROR_DATABASE_DOES_NOT_EXIST):
In the connection string, please check that the database server name and the instance name information is accurate. Sometimes, the server name is pointing to an old name or a generic one (BKUPEXEC) and we are unable to connect to the correct SQL Server instance properly.
If so, please check the registry on the media server and modify and/or create the following keys to reflect the real server name and the correct instance:
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Adamm |
Database Instance Name (by default BKUPEXEC)
Database Server Name
Try to start then the Backup Exec Device and Media service with this new configuration and check if no errors appear on the event viewer.
Issue/Introduction
The Backup Exec Device & Media Service does not start after a server name change or a Backup Exec version upgrade.
Was this article helpful?
thumb_up
Yes
thumb_down
No