Skip to main content
Logging, configuration files, and services for VMware

Agent logs and configuration details for VMware setup

Updated over a month ago

Enterprise Workloads Editions: βœ… Business | βœ… Enterprise | βœ… Elite

This topic contains information about the Enterprise Workloads agent configuration details and log files for your VMware setup.

Enterprise Workloads agent configuration details

The configuration file contains the configuration details that backup proxy requires to communicate with Druva Cloud.


πŸ“ Note

​We recommend that you do not modify the configuration file except when required. In scenarios where you must modify these configuration files, contact the Support team for assistance.


Configuration files

Version

OS

File Location

6.x.x

Linux

Druva configuration file

/etc/Phoenix/VMWARE/Phoenix.cfg

Proxy configuration file

/var/log/Phoenix/proxySetup.log

7.x.x

Linux

Druva configuration file

  • /etc/Druva/EnterpriseWorkloads/vmware/VMwareConfig.yaml

  • /etc/Druva/EnterpriseWorkloads/Config.yaml

Proxy configuration file

/var/log/Druva/EnterpriseWorkloads/ProxyConf.log

Enterprise Workloads agent log files

The Enterprise Workloads agent log files contain details of backups that the backup proxy performs. After every backup, a new log file is created in the following format:

  • Phoenix<YYYY/MM/DD>-<timestamp>.log

  • EnterpriseWorkloadsFL.<job_id>.<timestamp>.log

If backup proxy does not function as expected, you can share these log files with the Druva Support team.


πŸ“ Note

  • Druva retains logs for the last 32 agent activities on each server.

  • The debug logs on the VMware backup proxy contain IP addresses of all hops between your VMware backup proxy and Druva Cloud. This information is recorded solely for troubleshooting purposes.


You can find logs of all instances of backup proxy associated with a vCenter Server or ESXi at:

  • /var/log/Phoenix

  • /var/log/Druva/EnterpriseWorkloads

For more information, see article.


πŸ“ Note


​ The free space at this location should be at least 1% of your source data size.


Additional logs

In addition to a common log file, you can also find the following logs:

  • In a scenario where multiple instances of backup proxy are configured for a single instance of vCenter Server or ESXi,logs corresponding to each backup proxy are present in the backup proxy itself.

  • A virtual machine-specific log that records backup and restore operations from a virtual machine. For more information, see article.

  • vCenter credentials and warnings are available as logs at: /etc/Phoenix and /etc/Druva.

Enterprise Workloads agent services

The Druva process manages backups and restores of an instance of backup proxy. The Druva process also ensures that the Enterprise Workloads agent is running.

Service Name Information

Version

OS

Service Name

Service Restart command

6.x.x

Linux

Phoenix

service Phoenix restart

7.x.x

Linux

Druva-EnterpriseWorkloads

service Druva-EnterpriseWorkloads restart

Enterprise Workloads agent metadata

When you deploy backup proxy, the following metadata folders are created:

  • The restorestate folder
    This folder contains metadata that optimizes restores.

  • The <agentid> folder
    This folder contains metadata that optimizes backups.


πŸ“ Note


​The string <agentid> represents the type of Enterprise Workloads agent. The name 1 represents file server agents, the name 10 represents SQL server agents, and the name 20 represents backup proxy, respectively.


On SQL servers, the metadata folders are created at:

Version

Folder Location

6.x.x

/var/Phoenix

7.x.x

/var/Druva

Did this answer your question?