📝 Note
This article applies to
OS: Linux
Product edition: Enterprise Workloads
Overview
This article describes the procedure to enable and disable debug logging for VMWARE Druva backup proxy.
Enable the Debug Logging on VMWARE Backup Proxy:
Open the terminal and stop Agent Client Service.
Agent Version 6.x.x:
/etc/init.d/Phoenix stopAgent Version 7.x.x:
service Druva-EnterpriseWorkloads stopVerify if any Druva or Phoenix related processes.
Agent Version 6.x.x:
ps -ef| grep -i PhoenixAgent Version 7.x.x:
ps -ef | grep -i EnterpriseWorkloadsIf any process is still found running, kill the process with the following command:
Kill -9 <process id>Take a backup of the Configuration File
Agent Version 6.x.x:
/etc/Phoenix/FS/Phoenix.cfgAgent Version 7.x.x:
/etc/Druva/EnterpriseWorkloads/Config.yamland/etc/Druva/EnterpriseWorkloads/vmware/VMwareConfig.yamlOpen the file in VI editor and change the debug value from 0 to 9
Agent Version 6.x.x: change the value from
DEBUGLEVEL = 0 to DEBUGLEVEL = 9Agent Version 7.x.x: change the value from
debug_level: 0 to debug_level: 9Save the changes.
Then again Open the terminal and start Agent Client Service.
Agent Version 6.x.x:
/etc/init.d/Phoenix startAgent Version 7.x.x:
service Druva-EnterpriseWorkloads startInitiate the backup or the restore job.
Note:
Setting debug_level: 9 in below files affect debug logs in following logs:
/etc/Druva/EnterpriseWorkloads/Config.yaml--> ControlService.logs, All job logs(backup, restore, browse)/etc/Druva/EnterpriseWorkloads/vmware/VMwareConfig.yaml--> vmware.log, topology.log
Disable the Debug Logging on VMWARE Backup Proxy:
Open the terminal and stop Agent Client Service.
Agent Version 6.x.x:
/etc/init.d/Phoenix stopAgent Version 7.x.x:
service Druva-EnterpriseWorkloads stopVerify if any Druva or Phoenix related processes.
Agent Version 6.x.x:
ps -ef| grep -i PhoenixAgent Version 7.x.x:
ps -ef | grep -i EnterpriseWorkloadsIf any process is still found running, kill the process with the following command:
Kill -9 <process id>Take a backup of the Configuration File
Agent Version 6.x.x:
/etc/Phoenix/FS/Phoenix.cfgAgent Version 7.x.x:
/etc/Druva/EnterpriseWorkloads/Config.yamland/etc/Druva/EnterpriseWorkloads/vmware/VMwareConfig.yamlOpen the file in VI editor and change the debug value from 9 to 0
Agent Version 6.x.x: change the value from
DEBUGLEVEL = 9 to DEBUGLEVEL = 0Agent Version 7.x.x: change the value from
debug_level: 9 to debug_level: 0Save the changes.
Then again Open the terminal and start Agent Client Service.
Agent Version 6.x.x:
/etc/init.d/Phoenix startAgent Version 7.x.x:
service Druva-EnterpriseWorkloads startInitiate the backup or the restore job.
Note:
Setting debug_level: 0 in below files affect debug logs in following logs:
/etc/Druva/EnterpriseWorkloads/Config.yaml--> ControlService.logs, All job logs(backup, restore, browse)/etc/Druva/EnterpriseWorkloads/vmware/VMwareConfig.yaml--> vmware.log, topology.log
Collect the Logs from VMWARE Backup Proxy
After job completes or terminates then collect the below logs and zip in one folder
Logs from server location:
/var/log/Phoenix or /var/log/Druva
/var/log/messages
Failed or Terminated Job Logs from Druva Management Console.