How to enable continuous debugging of the Backup Exec Job Engine and the Remote Agent for Windows Servers by using the Windows Registry
| Article:TECH82942 | | | Created: 2002-01-19 | | | Updated: 2010-09-04 | | | Article URL http://www.symantec.com/docs/TECH82942 |
Problem
How to enable continuous debugging of the Backup Exec Job Engine and the Remote Agent for Windows Servers by using the Windows Registry
Solution
Under some circumstances, debugging using the Job Engine or Remote Agent using the Services console is inconvenient or insufficient; debugging configured using the Windows Registry allows for continuous debugging is an effective alternative when the debugging needs to occur after the server spontaneously restarts.
To enable debugging using the Windows Registry, perform the following:
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.
1. Run REGEDIT
2. Browse to the My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Logging (Figure 1).
Figure 1
3. Change the value from 0 to 1 (Figure 2).
Figure 2
4. Stop and restart the Backup Exec services for this change to take effect.
Note: From Backup Exec v11 there is no longer a need to stop and start the services as debugging will automatically start and stop when the registry key values has changed to enable debugging or to disable debugging.
NOTE:
When determining which method of debugging to perform on a system, remember that log files will continue to be written until this registry value is reset to zero and the Backup Exec services restarted*; although the Logs folder can be compressed to minimize the impact, logs will continue to accumulate. If untended, the logs will eventually fill up the disk space and can cause the server to fail.
When the problem is resolved or the necessary information is gathered and sent to support, disable the debugging and then unless instructed otherwise by support delete the debug logs from the Logs folder.
To enable debugging using the Windows Registry, perform the following:
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.
1. Run REGEDIT
2. Browse to the My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Logging (Figure 1).
Figure 1
3. Change the value from 0 to 1 (Figure 2).
Figure 2
4. Stop and restart the Backup Exec services for this change to take effect.
Note: From Backup Exec v11 there is no longer a need to stop and start the services as debugging will automatically start and stop when the registry key values has changed to enable debugging or to disable debugging.
NOTE:
When determining which method of debugging to perform on a system, remember that log files will continue to be written until this registry value is reset to zero and the Backup Exec services restarted*; although the Logs folder can be compressed to minimize the impact, logs will continue to accumulate. If untended, the logs will eventually fill up the disk space and can cause the server to fail.
When the problem is resolved or the necessary information is gathered and sent to support, disable the debugging and then unless instructed otherwise by support delete the debug logs from the Logs folder.
|
|
Related Articles
Legacy ID
250681
Article URL http://www.symantec.com/docs/TECH82942
Terms of use for this information are found in Legal Notices
Thank you.