How to enable debug logging to troubleshoot Backup Exec Deduplication Storage related Issues

Article: 100001042
Last Published: 2025-06-03
Ratings: 0 0
Product(s): Backup Exec

Problem
 

How to enable debug logging to troubleshoot Backup Exec Deduplication Storage related Issues
 

Solution
 

The logging for different Backup Exec deduplication processes is useful to troubleshoot and diagnose the problem seen with the below scenarios.
 
ISSUES LOG FILES
Deduplication Folder creation issue BE Install Path\logs\SGMON Log, Dedupe\log\PDDE-CONFIG.log
GRT Backup failure to Dedupe storage. BE Install Path\logs\SGMON log, BE Install Path\Logs\PDVFS logs, Deduplication Storage folder\log folder from BE server, PDplugin log.
Client side Backup issues  BE Install Path\logs\SGMON Log from Backup Exec server and remote server, PDplugin log from client server. Deduplication Storage folder\log folder from BE server.



 

Backup Exec Deduplication Storage configuration errors.
Backup Exec Deduplication Storage remains in discovering status.

From the Backup Exec User Interface, Launch the SGMON tool.
 
 

Capture the following processes: "Job Engine, RAWS, Agent Browser", "Backup Exec Server", "Device and Media", "Third party debug output", and "Capture to file".





From the Debug Monitor's -> Settings menu, check the "Enable verbose logging" setting in the Device and Media section.
 
 



ENABLING PDPLUGIN Logging from PD.CONF

Edit the pd.conf file present in the Backup Exec server's program directory (which is C:\Program Files\Veritas\Backup Exec" by default).  
Change the # LOGLEVEL line to LOGLEVEL = 10 and un-comment DEBUGLOG as well so that the log is created at the specified path.
 
 
 
 
 
Configure the Deduplication Storage Folder if troubleshooting a deduplication folder creation problem or recycle the Backup Exec services with the SGMON and pdplugin enabled to troubleshoot the discovering issue.

Collect the SGMON log along with  pdde-config.log from Deduplication Storage folder\log folder. Collect the pdplugin log as well.
 
Important: When troubleshooting is completed, revert the log settings, deselect verbose checkbox for device and media from SGMON and close it. This ensures the disk does not fill up.
 
 

Debug GRT Backups failure when targeted to Deduplication Storage :



1. Launch SGMON.exe from BE Install Path\SGMON.exe

2. Select  Job Engine, RAWS, Agent Browser, Backup Exec Server, Device and Media and Capture to file.  
    Go to Tools-> Settings -> Device and Media -> Turn on verbose logging.

Note: For larger size backup, the verbose setting for device and media can be enabled 15 to 20 minutes before the time when the user thinks the problem will occur. Keeping the verbose debug enabled for a long time may hamper server performance, so it is better to use it responsibly.

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.

3. Open the Registry Editor using Start-Run-Regedit
    Browse to the HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\PureDisk\PDVFS key.
 
 
 
 
Right Click on the PDVFS key and choose to create a new DWord value and give it the name DebugLevel.
 
Right Click on the new DebugLevel value.  Choose the Modify option and set the value to 3.
 
The DebugLevel value will need to be set to 6 or 7 to capture the Stream handler statements. This value should only be used if directed by a Technical Support team.
 
Important: When troubleshooting is complete,  change the value back to 0 to prevent this log from filling up the disk.
The PDVFS log gets created in the BE Install Path\Logs\PDVFS folder.
 
 
4. Run the backup which is failing and needs to be debugged. After the issue is reproduced, reset the debug settings.
 
Collect the SGMON Log, PDPLUGIN Log, PDVFS log along with the Backup Job Log.
 


Client Side Deduplication Issues (Remote Agent with Direct Access) :


1. Launch SGMON.exe on Backup Exec server and Remote server which is being backed up with Client side deduplication settings.
SGMON.exe is located at C:\Program Files\Veritas\Backup Exec\ on Backup Exec server.
SGMON.exe is located at C:\Program Files\Veritas\Backup Exec\RAWS on the client server.  

Note: Use the same settings as discussed in section "Backup Exec Deduplication Storage configuration errors or Storage remaining in discovering state"

2. Run the client side deduplication backup job and reproduce the job with the smallest data size backup.

Important: Remember to turn off all the extra logging.  Leaving it enabled will slow down the system and quickly fill the disk.


Backup Exec Open Cloud Storage Daemon is introduced from Backup Exec 21.3. The logging should be set to 1. The log is used to check any connection related problems while backing up to Cloud Deduplication Storage.

 

 

Was this content helpful?