How to enable debug notification in Backup Exec for Windows Servers

Article:TECH24686  |  Created: 2003-01-28  |  Updated: 2012-06-01  |  Article URL http://www.symantec.com/docs/TECH24686
Article Type
Technical Solution

Product(s)

Environment

Issue



How to enable debug notification in Backup Exec for Windows Servers


Solution



If it becomes necessary to debug notification for Backup Exec (tm) for Windows Servers, perform the following steps:
 
1. Open the registry editor of the backup server: click Start | Run | Regedit.exe
 
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.
  
2. Highlight the location :
 
For Backup Exec versions prior to 11.x:HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\SigLogger (Figure 1).
For Backup Exec version 11.x and later:HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SigLogger.
 
Figure 1
 
 
If the SigLogger key does not exist, it should be manually created. In order to create the key:
3. Highlight HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS ( for Backup Exec 11.x and later the key is now HKEY_LOCAL_MACHINE\SOFTWARE\Symantec)
4. Right-click 'Symantec' and select New | Key
5. Enter key name "SigLogger" (without the quotes).
 
After this, the Siglogger key that was just created is to be highlighted.
 
6. Right-click the 'Siglogger' key and select New | Key
7. Enter key name beserver.exe (Figure 2)
  
Figure 2
  
 

 With SigLogger highlighted again:
8. Right-click the 'Siglogger' key and select New | Key
9. Enter key name BkupExec.exe (Figure 3)
 
Figure 3
  

 Highlight the newly created beserver.exe. 
 
10. Right click 'beserver.exe' select New | DWORD (32-bit) Value
11. Enter Value Name: LogFilterFlag
12. Right-click 'LogFilterFlag' and enter 'ffffffff' and click OK. Please note this is a series of the letter 'f' eight times. (Figure 4)
 
Figure 4 
 
 
13. Right click 'beserver.exe' select New | String Value
14. Enter Value Name:  LogFilePath
15. Right-click ' LogFilePathand enter 'C:\nsserver.log(without quotes) and click OK.
 
The entries should look similar to Figure 7 below.
Figure 7 
  
Highlight the newly created BkupExec.exe. 
 
16. Right click 'BkupExec.exe' select New | DWORD (32-bit) Value
17. Enter Value Name: LogFilterFlag
18. Right-click 'LogFilterFlag' and enter 'ffffffff' and click OK. Please note this is a series of the letter 'f' eight times. (Figure 4) 
19. Right click 'BkupExec.exe' select New | String Value
20. Enter Value Name:  LogFilePath
21. Right-click ' LogFilePathand enter 'C:\nsclient.log(without quotes) and click OK.
22. Recycle Backup Exec Services, and restart the user interface.
 
There will be two logs generated, one for the server side, nsserver.log, and one for the client side, nsclient.log, respectively. It is not necessary to do both, as the majority of the output will be in the server side log, nsserver.log.
 
There is also a behavior that should be noted so that unnecessary troubleshooting does not take place. When reading the nsserver.log the port assignment configured in Backup Exec is listed as:
 
SMTPCONFIG PORT="25"
 
Example: <SMTPCONFIG PORT="25" ENABLED="TRUE"
  
Later in the log the port used may show: port =19
 
Example: 05/25/07 10:27:02 034674D0[ERROR]   NS SMTP error (server =192.168.0.1, port =19, recipient=administrator@domain.com, sender=administrator@domain.com)
 
If this occurs then the actual port being used my not be port 19. To verify the actual port it will be necessary to use Windows Network Monitor to capture network traffic and review the information for actual port usage.

TECH22054 
Troubleshooting Simple Mail Transfer Protocol notification with Microsoft Network Monitor in Windows 2000  

Additionally, if this occurs look for applications that could be blocking or filtering port 25. Review technotes TECH39199 and TECH36291
 for additional information.
 
TECH39199  
Backup Exec SMTP Mail Notifications are not sent when McAfee or other SMTP port/spam blocking software is installed on the SMTP or Backup Exec server 
TECH36291 
Simple Mail Transfer Protocol (SMTP) email notifications cannot be sent if McAfee VirusScan Enterprise is installed on the SMTP server. 



Legacy ID



256517


Article URL http://www.symantec.com/docs/TECH24686


Terms of use for this information are found in Legal Notices