Skip to main content

How can we help you?

Druva Documentation

Phoenix agent logs and configuration details

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

This article provides information about the Phoenix agent configuration details and logs for an MS-SQL server setup.

Phoenix agent log files

The Phoenix agent log files contain details of backups that the Phoenix agent performs. After every backup, Druva Phoenix creates a new log file in the Phoenix<YYYY/MM/DD>-<timestamp>.log format. If Phoenix agent does not function as expected, you can share these log files with the Druva Support team.

Note: Druva Phoenix retains logs for the last 32 agent activities on each server. 

On all versions and editions of an MS-SQL server, you can find the logs at C:\ProgramData\Phoenix\FS\logs. The free space at this location should be at least 1% of your source data size. 

Note: After each backup and restore, Druva Phoenix performs a rollover of the accompanying logs. If you encounter an error during a backup or restore, check the log file for errors at the time of the backup or restore operation. 

Additional logs

In addition to the Druva Phoenix logs, Druva Phoenix creates Windows Event Viewer logs with a .evt extension. To know how to manage these logs, see this article in the Microsoft library. If you encounter errors during backup or restore, look for errors with source = VSS, MSSQLSERVER, or SQLVDI.

Phoenix agent configuration details

The Phoenix.cfg file contains the configuration details that Phoenix agents require to communicate with Druva Phoenix Master. 

Note: We recommend that you do not modify Phoenix.cfg except when required. In scenarios where you must modify these configuration files, contact the Druva Support team for assistance. 

You can find the Phoenix agent configuration details at the following locations:

Operating System Location
Windows Server
2008, 2012, 2016, 2019

Phoenix agent services

On Windows servers, Phoenix agent Client Service manages backups and restores. The PhoenixCPH service on Windows servers ensures that the Phoenix agent Client Service is running. 

Note: If Phoenix agent stops working, PhoenixCPH (Windows) starts Phoenix agent. 

Phoenix agent metadata

When you install Phoenix agents on your servers, Druva Phoenix creates the following metadata folders in the Phoenix folder:

  • The logs folder
    This folder contains logs for backup and restore jobs for MS-SQL server.
  • The state folder
    This folder contains metadata that optimizes restores. 
  • The stats folder
    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. 

On MS-SQL servers, the metadata folders are created at C:\ProgramData\Phoenix\SQL.

Additional metadata

At the time of restore, Druva Phoenix creates a database_files.txt file at <Drive>\restore\<snapshot>\<Request ID>. This file contains details of how the database files are mapped to the database, and how the database is mapped to its instance in a Unicode format. You require this file to manually attach the database to an instance at the time of restoring to a different server.