Skip to main content
All CollectionsKnowledge BaseEnterprise WorkloadsHow To - Enterprise Workloads
How to enable or disable debug logging for Druva VMWARE backup proxy
How to enable or disable debug logging for Druva VMWARE backup proxy
Updated over a week ago

📝 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:

  1. Open the terminal and stop Agent Client Service.

    Agent Version 6.x.x: /etc/init.d/Phoenix stop

    ​Agent Version 7.x.x: service Druva-EnterpriseWorkloads stop

  2. Verify if any Druva or Phoenix related processes.

    Agent Version 6.x.x: ps -ef| grep -i Phoenix

    Agent Version 7.x.x: ps -ef | grep -i EnterpriseWorkloads

  3. If any process is still found running, kill the process with the following command:

    Kill -9 <process id>

  4. Take a backup of the Configuration File

    Agent Version 6.x.x: /etc/Phoenix/VMWARE/Phoenix.cfg

    Agent Version 7.x.x: /etc/Druva/EnterpriseWorkloads/Config.yaml and /etc/Druva/EnterpriseWorkloads/vmware/VMwareConfig.yaml

  5. Open 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 = 9

    Agent Version 7.x.x: change the value from debug_level: 0 to debug_level: 9

  6. Save the changes.

  7. Then again Open the terminal and start Agent Client Service.

    Agent Version 6.x.x: /etc/init.d/Phoenix start

    Agent Version 7.x.x: service Druva-EnterpriseWorkloads start

  8. Initiate 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:

  1. Open the terminal and stop Agent Client Service.

    Agent Version 6.x.x: /etc/init.d/Phoenix stop

    ​Agent Version 7.x.x: service Druva-EnterpriseWorkloads stop

  2. Verify if any Druva or Phoenix related processes.

    Agent Version 6.x.x: ps -ef| grep -i Phoenix

    Agent Version 7.x.x: ps -ef | grep -i EnterpriseWorkloads

  3. If any process is still found running, kill the process with the following command:

    Kill -9 <process id>

  4. Take a backup of the Configuration File

    Agent Version 6.x.x: /etc/Phoenix/VMWARE/Phoenix.cfg

    Agent Version 7.x.x: /etc/Druva/EnterpriseWorkloads/Config.yaml and /etc/Druva/EnterpriseWorkloads/vmware/VMwareConfig.yaml

  5. Open 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 = 0

    Agent Version 7.x.x: change the value from debug_level: 9 to debug_level: 0

  6. Save the changes.

  7. Then again Open the terminal and start Agent Client Service.

    Agent Version 6.x.x: /etc/init.d/Phoenix start

    Agent Version 7.x.x: service Druva-EnterpriseWorkloads start

  8. Initiate 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

  1. Logs from server location:

    1. /var/log/Phoenix or /var/log/Druva

    2. /var/log/messages

  2. Failed or Terminated Job Logs from Druva Management Console.

See also

Did this answer your question?