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

This article applies to:

  • OS: Windows and Linux

  • Product edition: Phoenix

Overview

This article describes the procedure to enable and disable debug logging for Hybrid Workloads Agent Client service. Ensure that there are no backup or restore jobs scheduled to run for the NAS Shares while enabling or disabling debug logging for the agent. Druva requires you to cancel all jobs that are currently running before performing the following tasks.

Enable and disable debug logging for a Druva NAS proxy

Enable the Debug Logging on Windows NAS proxy:

  1. Open Services console(services.msc) and stop Agent Client Service.
    ​​Agent Version 6.x.x: Hybrid Workloads Agent Client Service.
    ​​Agent Version 7.x.x: Druva-EnterpriseWorkloads Service

  2. Open Task Manager and kill all Druva or Phoenix related processes.

  3. Take a backup of the Configuration File
    ​​Agent Version 6.x.x: C:\ProgramData\Phoenix\NAS\Phoenix.cfg
    ​Agent Version 7.x.x: C:\ProgramData\Druva\EnterpriseWorkloads\Config.yaml and C:\ProgramData\Druva\EnterpriseWorkloads\nas\Config.yaml

  4. Open the file in notepad 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

  5. Save the changes.

  6. Then again Open Services console(services.msc) and start Agent Client Service.

    ​Agent Version 6.x.x: Hybrid Workloads Agent Client Service.

    Agent Version 7.x.x: Druva-EnterpriseWorkloads Service

  7. Initiate the backup or the restore job.

Disable the Debug Logging on Windows NAS proxy:

  1. Open Services console(services.msc) and stop Agent Client Service.
    ​​Agent Version 6.x.x: Hybrid Workloads Agent Client Service.
    ​​Agent Version 7.x.x: Druva-EnterpriseWorkloads Service

  2. Open Task Manager and kill all Druva or Phoenix related processes.

  3. Take a backup of the Configuration File
    ​​Agent Version 6.x.x: C:\ProgramData\Phoenix\NAS\Phoenix.cfg
    ​Agent Version 7.x.x: C:\ProgramData\Druva\EnterpriseWorkloads\Config.yaml and C:\ProgramData\Druva\EnterpriseWorkloads\nas\Config.yaml

  4. Open the file in notepad 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

  5. Save the changes.

  6. Then again Open Services console(services.msc) and start Agent Client Service.

    ​Agent Version 6.x.x: Hybrid Workloads Agent Client Service.

    Agent Version 7.x.x: Druva-EnterpriseWorkloads Service

  7. Initiate the backup or the restore job.

Collect the Logs from Windows NAS proxy

After job completes or terminates then collect the below logs and zip in one folder

  1. Logs from server location:

    1. C:\ProgramData\Phoenix or C:\ProgramData\Druva

    2. Windows Application and System event logs in the .evt or .evtx format.

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

Enable the Debug Logging on Linux NAS 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/NAS/Phoenix.cfg

    Agent Version 7.x.x: /etc/Druva/EnterpriseWorkloads/Config.yaml and /etc/Druva/EnterpriseWorkloads/nas/Config.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.

Disable the Debug Logging on Linux NAS 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/NAS/Phoenix.cfg

    Agent Version 7.x.x: /etc/Druva/EnterpriseWorkloads/Config.yaml and /etc/Druva/EnterpriseWorkloads/nas/Config.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.

Collect the Logs from Linux NAS 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.

Upload the Logs

  • If the zip/log file is below 4.5 MB then you can directly send us by attaching it to the email or uploading via support portal on the case.

  • Else, Go to https://upload.druva.com/

    • Enter the case number in the Ticket Number field.

    • Click Choose File and add the compressed files to upload.

    • Click Upload.

    • Notify the support engineer about the logs uploaded through Portal by responding to the ongoing support ticket.

See also: How to collect the detailed job logs - Druva Documentation

Related Articles
How to enable or disable debug logging for SQL server agent
How to enable or disable debug logging for Druva VMWARE backup proxy
How to enable or disable debug logging for File Server Agent
How to enable or disable debug logging for Hyper V host
Logging, configuration files, and services for File Server
Did this answer your question?