Enterprise Workloads Editions: ✅ Business | ✅ Enterprise | ✅ Elite
Administrators and DBAs can monitor progress of the backup and restore jobs using the progress logs and detailed logs generated for Oracle database jobs. These logs are located at the /var/log/Phoenix/Oracle (for agent version 6.x or earlier) or /var/log/Druva/EnterpriseWorkloads/ (for agent version 7.x or later)location. This directory contains the following files:
main_service.log(for agent version 6.x or earlier) or/var/log/Druva/EnterpriseWorkloads/oracle/oracle.log(for agent version 7.x or later): Use the log to monitor the Oracle process./ORACLE/logs/restore/<backupsetID>/<jobID_Attempt_No>./(for agent version 6.x or earlier) or/var/log/Druva/EnterpriseWorkloads/oracle/restore/<backupsetID>/<jobID_Attempt_No>/(for agent version 7.x or later): Contains logs generated for the restore job./ORACLE/logs/backup/<backupsetID>/<jobID_Attempt_No>./(for agent version 6.x or earlier) or/var/log/Druva/EnterpriseWorkloads/oracle/backup/<backupsetID>/<jobID_Attempt_No>/(for agent version 7.x or later): Contains logs generated for the backup job.
The following video illustrates the process.
The Logs tab displays the following information:
Progress Logs: Displays the summary of the progress of the backup and restore jobs triggered for Oracle databases. The progress logs of the backup jobs also include RMAN Logs containing the RMAN script and the RMAN output. Therefore, you can use the progress logs to monitor the RMAN activities in detail.
The progress logs provide a detailed status of the job as follows:📝 Note
The Log Requests jobs do not display the progress log.The start and completion time of the job initiated for a database
The total data estimated for backup
The version of the Hybrid Workloads agent deployed in your environment
The name of the database for which the job is initiated
The channel allocated to a RAC node
The start and completion time of datafiles backups
The start and completion time of control file backup
The start and completion time of system parameter file backup
The start and completion time of archive log backup
The job status for databases
The total data files and the total data to download in case of restore
📝 Note
For the RAC databases, the node information is displayed only after the job is completed.
The following screenshot depicts progress logs for a sample backup job:
Detailed Logs: Displays detailed logs for the backup and restore operations of that job. You can use the log files to analyze and troubleshoot the issues that you might encounter while performing a task. Detailed logs are available only after the completion of the upload job. Druva allows you to request for the detailed logs of the job using the Request Details Logs button. You can request for detailed logs only when the job is in progress or running. Druva triggers a corresponding Log Request job that uploads the logs to cloud. Once the job is completed, you can download the logs by clicking the Download Detail Logs button .Detailed logs are available for download only after they are uploaded to cloud. If you try to download the logs before they are uploaded to cloud, you might have to wait for some time for the logs to be available for download.
You must download the requested logs within 7 (for agent version 6.x or earlier) or within 30 days (for agent version 7.x or later) days of triggering the request. The job details are available on the Management Console for 180 days. For assistance in resolving your issues, you can share the log files with the Support team.
📝 Notes
The Download Detail Logs button remains disabled till the time download is in progress or the user refreshes the page.
For the RAC databases, the logs may not be uploaded for some of the nodes. In that case, you can either proceed with downloading partial logs or you can request for full logs.
Procedure
On the Jobs page, click the required backup or restore job for which you want to request the detailed logs.
Click the Logs tab.
In the Detailed Logs section, click Download Detail Logs.
Extract the log files from the downloaded
PhoenixLogs-<job_id>.zip(for agent version 6.x or earlier) orOracle.<date>-<time>-<jobid>.zip(for agent version 7.x or later) folder.
The detailed log file (log.zip) contains the following files:
File Name
| Agent Version
6.1.3-466835.x86_64 or earlier
| Agent Version
7.x or later
|
Druva configuration file | Phoenix.yml | OraclePlugin.yml |
Main Service Log | main_service.log | oracle.log |
RMAN Log containing the RMAN script and the RMAN output |
|
|
SBT Client Log | sbtclient.log | sbtclient.log |
IOServer LOG | IOServer.log |
|
Metadata file | Metadata.json | Metadata.json |
Agent Job logs | Phoenix.log | OracleJob.log |
Enable and disable debug logging for Oracle Direct to Cloud
Enable debug logging
Log in to the Oracle Server.
Stop the Phoenix Oracle service using the command:
service PhoenixOracle stop(for agent version 6.x or earlier)
service Druva-EnterpriseWorkloads stop(for agent version 7.x or later)
Check if any Phoenix processes are still running. If any Phoenix process is still running, kill the process. Use the following commands:ps -ef| grep -i PhoenixOracle(for agent version 6.x or earlier)ps -ef| grep -i Druva-EnterpriseWorkloads(for agent version 7.x or later)Kill -9 <process id>Browse to /etc/PhoenixOracle/Phoenix.yml and create a backup of Phoenix.yml (for agent version 6.x or earlier)
Browse to /etc/Druva/EnterpriseWorkloads/oracle/OraclePlugin.yml (for agent version 7.x or later) and create a backup of OraclePlugin.ymlOpen Phoenix.yml (for agent version 6.x or earlier) in the vi editor and change
DEBUGLEVEL = 0
to
DEBUGLEVEL = 9
Open OraclePlugin.yml (for agent version 7.x or later) in the vi editor and change
debug_level = 0
to
debug_level = 9Save the changes.
Start the Phoenix Oracle Agent Service
service PhoenixOracle start(for agent version 6.x or earlier)
service Druva-EnterpriseWorkloads start(for agent version 7.x or later)Initiate a backup or restore job.
Disable debug logging
Log in to the Oracle Server.
Stop the Phoenix Oracle service using the command:
service PhoenixOracle stop(for agent version 6.x or earlier)
service Druva-EnterpriseWorkloads stop(for agent version 7.x or later)
Check if any Phoenix processes are still running. If any Phoenix process is still running, kill the process. Use the following commands:
ps -ef| grep -i PhoenixOracle (for agent version 6.x or earlier)
ps -ef| grep -i Druva-EnterpriseWorkloads (for agent version 7.x or later)
Kill -9 <process id>Browse to /etc/PhoenixOracle/Phoenix.yml and create a backup of Phoenix.yml (for agent version 6.x or earlier)
Browse to /etc/Druva/EnterpriseWorkloads/oracle/OraclePlugin.yml (for agent version 7.x or later) and create a backup of OraclePlugin.ymlOpen Phoenix.yml in the vi editor and change
DEBUGLEVEL =9
to
DEBUGLEVEL = 0
Open OraclePlugin.yml (for agent version 7.x or later) in the vi editor and change
debug_level = 9
to
debug_level = 0Save the changes.
Start the Phoenix Oracle Agent Service
service PhoenixOracle start (for agent version 6.x or earlier)
service Druva-EnterpriseWorkloads start(for agent version 7.x or later)