This topic contains information about the Enterprise Workloads agent configuration details, metadata, and log files for File servers.
Agent log files
The Enterprise Workloads agent log files contain details of backups that the Enterprise Workloads agent performs. After every backup, a new log file is created in thePhoenix <YYYY/MM/DD>-<timestamp>.logformat. If Enterprise Workloads agent 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.
Log location on file servers
You can find the Enterprise Workloads agent log files at the following locations:
Windows | Linux |
Windows Server | CentOS, RHEL, SLES, Ubuntu |
|
|
📝 Note
On Windows Servers, the agent writes all the logs to
C:\ProgramData\Phoenix\FS(for agent version prior to 7.0.0)C:\ProgramData\Druva\EnterpriseWorkloads\fs(for agent version 7.0.0 and later)
On Linux servers, Enterprise Workloads agent writes logs to
/var/log/Phoenix/FS(for agent version prior to 7.0.0)/var/log/Druva/EnterpriseWorkloads/fs/(for agent version 7.0.0 and later)
The free space at these locations should be at least 1% of your source data size.
Configuration details
The following files contain the configuration details to communicate with Druva cloud.
Phoenix.cfgfile atC:\ProgramData\Phoenix\FS(for agent version prior to 7.0.0)Config.yamlfile atC:\ProgramData\Druva\EnterpriseWorkloads\fs(for agent version 7.0.0 and later)
📝 Note
We recommend that you do not modify these files except when required. In scenarios where you must modify these configuration files, contact the Support for assistance.
Configuration details on file servers
You can find the agent configuration details at the following locations:
Windows | Linux |
Windows Server | CentOS, RHEL, SLES,Ubuntu |
|
|
Workloads agent services
On Windows servers, Hybrid Workloads agent Client Service / Druva-EnterpriseWorkloads Service manages backups and restores. The PhoenixCPH / Druva-EnterpriseWorkloadsSVC service on Windows servers ensures that the Hybrid Workloads agent Client Service / Druva-EnterpriseWorkloads is running. On Linux servers, the Phoenix / Druva-EnterpriseWorkloads process ensures that the agent is running.
📝 Note
If the agent stops working, PhoenixCPH / Druva-EnterpriseWorkloadsSVC (Windows) or Phoenix / Druva-EnterpriseWorkloads (Linux) starts Druva.
Workloads agent metadata
When you install agents on your file servers, the following metadata folders are created in the Druva folder:
The
logsfolder
This folder contains logs for backup and restore jobs for File server.The
statefolder
This folder contains metadata that optimizes restores.The
statsfolder
This folder contains metadata that optimizes backups.
📝 Note
The logs folder contains three folders, Backup, Restore, and Upload, respectively. Each of these folder contains <backupset_id> folders. The string <backupset_id> represents the unique identification number of the backup set configured on the server.
Metadata folders on file servers
On Windows File servers, the metadata folders are created at:
C:\ProgramData\(for agent version prior to 7.0.0)C:\ProgramData\Druva\EnterpriseWorkloads\fs(for agent version 7.0.0 and later)
On Linux (RHEL, CentOS, Ubuntu, SELS) file servers, the metadata is created at:
/var/Phoenix/FS(for agent version prior to 7.0.0)/var/Druva/EnterpriseWorkloads/fs(for agent version 7.0.0 and later)
Frequently Asked Questions (FAQs)
How to automatically delete older job logs of backup sets on a File Server during a backup or restore?
You can set the threshold value by using the OLDER_LOGS_DELETION_AGE parameter in the configuration file to delete older job logs, thereby saving space on the File Server. The default value is 180 days. The minimum allowed value is 1 day.