On the client machine - 

• Run the following command from an Administrative CMD prompt from the "C:\Program Files (x86)\Veritas\Veritas DLO\DLO" or "C:\Program Files (x86)\Veritas\Veritas DLO\DLO  folder":

DLOLoggingu.exe -E dloclientu.exe -L Verbose -LS 500

• Exit the DLO Client console from the Tray icon and reopen to fully enable logging

• Reproduce the issue, so that is recorded in the logs.

On the DLO Administration Server - 

• Run the following command from an Administrative CMD prompt from the DLO installation directory; "C:\Program Files\Veritas\Veritas DLO" by default

DLOLoggingu.exe -E DLOAdminsvcu.exe -L Verbose -LS 500    (to Debug issues with the DLO Admin Service)

DLOLoggingu.exe -E DLOConsoleu.exe -L Verbose -LS 500   (to Debug issues with the DLO Admin Console)

DLOLoggingu.exe -E DLOMaintSvcu.exe -L Verbose -LS 500   (to Debug issues with the Maintenance\Grooming process)

DLOLoggingu.exe -E DLORemInstDlgs.dll -L Verbose -LS 500   (to Debug issues with push installs)

*Note*: If the command reports "Failed to find OS bitness. Error=0x5" you have not run this in an Administrative CMD prompt. Correct that and rerun the command.

• Close the DLO Administration Console if open and then restart the Veritas DLO and Mindtree StoreSmart services
• Reproduce the issue, so that is recorded in the logs.

• Collect and send the logs. Use one of the following utilities to gather the logs :
  1. Use the DLOGather Utility to generate a .cab file. This utility is installed with DLO 7.5x or later. See article https://supportbackupexec.cloud.com/support-home/kbsearch/article?articleNumber=100009766&articleTitle=how-to-collect-dlo-serverdesktop-log-file-information-needed-by-technical-support-for-troubleshooting-purposes on how to use it. 
  2. Use Veritas Quick Assist Utility to generate a .vdbz file. This utility is installed with DLO 9.6 or later. See article https://supportbackupexec.cloud.com/support-home/kbsearch/article?articleNumber=100051060&articleTitle=how-to-collect-logs-of-local-and-remote-servers-using-vqa on how to use it. 

• To Disable logging via command line, replace "Verbose" in the above commands, with "Disable" (i.e. DLOloggingu.exe -E dloclientu.exe -L Disable )

On the DLO server:

1. Go to HKEY_CURRENT_USER\Software\Veritas\Components
   • Create the key Components key if it does not exist
   • Create a new key called debugstream
     • Create a new Key below debugstream called dloconsoleu.exe
     • Set the value of (Default) to  0xFFFFFFFF
2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\Components   
   • Create the key Components key if it does not exist
   • Create a new key called debugstream
     • Create a new Key below debugstream called dloconsoleu.exe
       • Set the value of (Default) to  0xFFFFFFFF
     • Create a new Key below debugstream called dloadminsvcu.exe
       • Set the value of (Default) to  0xFFFFFFFF
     • Create a new Key below debugstream called dlomaintsvcu.exe
       • Set the value of (Default) to  0xFFFFFFFF
   • Restart the DLO services

• To turn off debug logging, the "0xFFFFFFFF" values should be changed to a "0" and the DLO services restarted.

On the DLO Client 

1. Go to HKEY_CURRENT_USER\Software\Veritas\Components
   • Create the key Components key if it does not exist
   • Create a new key called debugstream
     • Create a new Key below debugstream called dloclientu.exe
     • Set the value of (Default) to  0xFFFFFFFF
2. Go to HKEY_CURRENT_USER\SOFTWARE\Veritas\Veritas DLO\Logger
   • Create the following "String Value" (REG_SZ)) keys if they do not exist and set the values:
     • BackupFileCount        set the value to  50
     • FileSize                        set the value to  10
     • LogCmpression          set the value to  1
     • ThresholdLevel           set the value to  4

• Restart the DLO client (File- Exit in the DLO Agent console)

• To turn off debug logging, the "0xFFFFFFFF" values should be changed to a "0" and the DLO Agent restarted. 

Notes about the logs: