1. Support
  2. Knowledge base
  3. 100029016

How to enable Debugging for Hyper-V

Article: 100029016
Last Published: 2019-01-15
Ratings: 0 0
Product(s): Backup Exec

Problem

How to enable Debugging to troubleshoot Hyper-V backup\restore

Solution

Use the Debug Monitor for simple One Click Debug on each Server by selecting the Icon for Hyper-V.

If the debug monitor is unavailable enable debug logging via the registry.  - https://www.veritas.com/support/en_US/article.100029014


Set Debug on the Backup Exec (BE) server, the Hyper-V Host, and VM that is part of the issue: 

Open Debug Monitor on each server. 
  1. On the BE server:
    1. Select the following items from the main screen of Debug Monitor: Job Engine, RAWS, Agent Browser, Backup Exec Server, Device and Media, Catalog, and Capture to File.
    2. Click Clear Log
    3. Inside the Tools\Settings dialog, select Job Engine & Remote Agent 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) 
  2. On the Hyper-V Host:
    1. Select the following items from the main screen of Debug Monitor:  RAWS, and Capture to File.
    2. Click Clear Log
    3. Inside the Tools\Settings dialog, select Job Engine & Remote Agent 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)
  3. On the Virtual Machine (VM) (Only for an Application GRT Backup, or any Granular GRT Restore into the VM):
    1. Select the following items from the main screen of Debug Monitor: RAWS and Capture to File.
    2. Click Clear Log
    3. Inside the Tools\Settings dialog, select Job Engine & Remote Agent 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. Run the job and reproduce the issue.
    1. Select the smallest job that will reproduce the problem.
    2. Run this while no other jobs are running, if possible.
    3. Wait for the error to occur.
  5. Collect and send the logs:
    1. Run the Veritas Quick Assist tool on each server to collect and send logs. More detail on this tool can be found in https://www.veritas.com/support/en_US/vqa
    2. Be sure to select Full logs for support
    3. After the Tool has completed the upload of logs from each server to the FTP site, Save and send the Job Log of the job by replying to the Technician Email or posting it to the case at https://my.veritas.com
  6. 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?

Article Languages