How to enable Debugging for SQL

Article: 100027798
Last Published: 2018-05-16
Ratings: 0 0
Product(s): Backup Exec

Problem

How to enable Debugging to troubleshoot SQL backup\restore issues

Solution

Debug Steps:
Set Debug on the Backup Exec (BE) server and each SQL server: 
 
Open Debug Monitor on each server. For more details on the Debug Monitor, see - https://www.veritas.com/support/en_US/article.100017069
  1. On the BE server:
    1. Click the Capture icon (third from left in the Ribbon Bar) and hover over the icons on the left-hand side until Microsoft SQL Server Agent pops up and click it.  This will select or check the following items from the selection screen to be debugged: Job Engine, Agent for Windows, Agent Browser, Backup Exec Server, Device and Media, Catalog, and Third party debug output. These selections can be individually checked also by using the Custom selection.
    2. Verify in the Ribbon Bar, Capture to File is checked / selected.
    3. Click the Settings icon (Sprocket, last icon on the right of the Ribbon Bar) to open the settings window.  Select Job Engine & Agent for Windows on the left. Then select Enable Job Engine and Remote Agent Debug outside of SGMon. (Note this will remain in debug mode until this option is turned off)
    4. Click the Edit tab at the top of the debugger and click Clear Log.
    5. Click the Start Capturing icon (Green, first icon from left in the Ribbon Bar). Do this right before running the job.
  2. On each remote SQL server:
    1. Click the Capture icon (third from left in the Ribbon Bar) and select Custom and then check the following items from the selection screen to be debugged: Job Engine, Agent for Windows, Agent Browser. 
    2. Verify in the Ribbon Bar, Capture to File is checked / selected.
    3. Click the Settings icon (Sprocket, last icon on the right of the Ribbon Bar) to open the settings window.  Select Job Engine & Agent for Windows on the left. Then select Enable Job Engine and Remote Agent Debug outside of SGMon. (Note this will remain in debug mode until this option is turned off)
    4. Click the Edit tab at the top of the debugger and click Clear Log.
    5. Click the Start Capturing icon (Green, first icon from left in the Ribbon Bar).  Do this right before running the job.
  3.  Run the job that reproduces the issue. 
    1. Select the smallest job that will reproduce the problem. You can right click the job and run with debugger enabled.  Run this job while the debuggers from the first steps are running.
    2. Run this while no other jobs are running, if possible.
    3. Wait for the error to occur.
  4. Collect and send the logs:
    1. Run the Veritas Quick Assist tool on each server to collect and send logs. For more details on this tool, they can be found in https://www.veritas.com/support/en_US/vqa
    2. Be sure to select Full logs for support 
    3. After the VQA Tool has has completed, either upload the resulting log file from each server to the FTP site or uploading it to the case via the web portal. Save and send the Job Log of the job by replying to an email from the case.
  5. Debugs should be turned off after the issue is resolved and the logs can be deleted. Each step of the debugs mentioned above need to be undone.
 
   
Notes about the logs:
The logs are created under -
BE Server - Program Files\veritas\Backup Exec\Logs
Remote servers - Program Files\veritas\Backup Exec\RAWS\Logs
The following logs create a new file each time BE services restart/debug is turned on:
ServerName-BEngine##.log      
ServerName-BERemote##.log  
The following logs append (single log file):
ServerName-SGMon.log

Was this content helpful?