Former mediaserver still has EMM registry keys
Hi
We have two servers (Windows 2008R2, nb client 7.6.0.1) and they used to be mediaservers.
Mediaserver software was uninstalled, servers rebooted and ordinary client software was installed.
Everything is working fine, except that both these servers windows eventlog is filled up with errors.
"EMM interface initialization failed, status = 333"
When I asked for the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup"
I found this key ""EMMSERVER"="masterservername" in "CurrentVersion\Config"
Simply removing the servername or the entire key does not stop the eventlog from piling up with error messages.
Does anyone know which registry keys that also have to be deleted ?
Regards
Per
Hi again
We edited the registry keys:[HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion]
"Install Type"="NetBackup Media Server" (Changed to "Netbackup Client")
"MediaServerInstalled"=dword:00000001 (Changed dword to 0)[HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config]
"EMMSERVER"="*_masterserver_name_*" (ERASED THIS WHOLE KEY)This did not change anything.
I got access to the server and compared it to a normal client installation and found many Netbackup services that should not be there.
Normal client, services running:
Netbackup Client Service Automatic
Netbackup Dedupllication Multi-Threaded Agent Automatic
Netbackup Discovery Framework Automatic
Netbackup Legacy Client Service Automatic
Netbackup Legacy Network Service Automatic
Symantec Private Branch Eschange AutomaticFormer Media Server, services running:
NetBackup Client Service
NetBackup CloudStore Service Container
NetBackup Deduplication Multi-Threaded Agent
NetBackup Device Manager
NetBackup Discovery Framework
NetBackup Legacy Client Service
NetBackup Legacy Network Service
NetBackup Service Layer
NetBackup Service Monitor
NetBackup Volume ManagerSolution:
We issued bpdown and set a lot of the extra services to manual and Volume Manager to disabled and then ran bpup, now all errors in the eventlog has stopped.