- Veeam Support Knowledge Base
- How to Collect Logs for Veeam Plug-in for Oracle RMAN
How to Collect Logs for Veeam Plug-in for Oracle RMAN
| KB ID: | 2871 |
| Product: | Veeam Backup & Replication | 10 | 11 | 12 | 12.1 | 12.2 | 12.3 | 12.3.1 | 12.3.2 | 13 | 13.1 |
| Published: | 2019-01-25 |
| Last Modified: | 2026-11-03 |
| Languages: | JP |
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
Purpose
Solution
- Collect diagnostic information as documented in the five sections below.
- Combine the data into a single .zip file.
- Attach the zip file to the Veeam Support case.
1) Veeam Plugin Logs on Veeam Servers
Collect logs found within the plugin folder indicated below on the Veeam Backup Server and all Backup Repositories*.
*For repositories other than Windows and Linux, the log files will be located on the Gateway server associated with the repository.
Veeam Backup & Replication 13.0 and later
- Veeam Backup Server
%ProgramData%\Veeam\Backup\Plugin\
- Windows Repository
%ProgramData%\Veeam\Backup\SharedAgents\{Backup Name}_{ID}\ - Linux Repository
/var/log/VeeamBackup/SharedAgents/{Backup Name}_{ID}/
Earlier versions
- Veeam Backup Server / Windows Repository
%ProgramData%\Veeam\Backup\Plugin
- Linux Repository
/var/log/VeeamBackup/Plugin
For Managed Backups
If the backup is managed by Veeam Backup & Replication, please also collect the following:
- From the Veeam Backup Server, all logs within:
%programdata%\Veeam\Backup\Rescan\
- Job logs as per KB1832
2) Veeam Plugin Logs on the Oracle Server
For Oracle Running on Linux, Oracle Solaris, or AIX
- PlugIn Logs — Collect plugin logs found within the folder indicated below on the Oracle Server.
/tmp/veeam_plugin_logs/
The command below will automate the collection of logs from the /tmp/veeam_plugin_logs/:
cd /tmp/veeam_plugin_logs/ && tar -cvf - . | gzip -9 > ~/$(hostname)-$(date +"%Y-%m-%d_%H-%M-%S-%z-")-veeam_plugin_logs.tar.gz && cd -
The command above is formatted to allow for universal usage with Linux, Solaris, and AIX. The output file will be written to the home folder of the account running the command. The exported log file's name will be unique and include the hostname, date stamp, and timezone.
- Oracle Proxy Logs — Collect plugin logs found within the folder indicated below on the Oracle Server.
/tmp/OracleProxyLogs/
The command below will automate the collection of logs from the /tmp/OracleProxyLogs/ :
cd /tmp/OracleProxyLogs/ && tar cvf - . | gzip -9 > ~/$(hostname)$(date +"%Y-%m-%d_%H-%M-%S-%z-")-OracleProxyLogs.tar.gz && cd -
The command above is formatted to allow for universal usage with Linux, Solaris, and AIX. The output file will be written to the home folder of the account running the command. The exported log file's name will be unique and include the hostname, date stamp, and timezone.
- Managed Deployment Logs — If the backup is managed by Veeam Backup & Replication, collect from the folder:
/var/log/VeeamBackup/
- VeeamDeploymentCli.log
- VeeamDeploymentDll.log
- VeeamDeploymentSupervisor.log
- VeeamDeploymentSvc.log
- VeeamDeploymentVcpServer.log
- VeeamEnvironmentSvc.log
- VeeamImmutableRepoSvc.log
- VeeamInstaller.Default.log
- VeeamTransportCli.log
- VeeamTransportSvc.log
Alternatively, collect all logs from the /var/log/VeeamBackup/ folder with this command:
cd /var/log/VeeamBackup/ && sudo tar -cvf - . | gzip -9 > ~/$(hostname)-$(date +"%Y-%m-%d_%H-%M-%S-%z-")-veeam_deployment_logs.tar.gz && cd -
For Oracle Running on Windows
- Collect plugin logs found within the folder indicated below on the Oracle Server.
%ProgramData%\Veeam\Backup\RmanPluginLogs\
- If the backup is managed by Veeam Backup & Replication, please also collect the following logs from the folder: C:\ProgramData\Veeam\Backup\
- Svc.VeeamInstaller.log
- Svc.VeeamInstallerDll.log
- Svc.VeeamTransport.log
- VssProxy.log
3) RMAN Operation Logs
Save information about failed RMAN operations. This can be achieved in different ways, as shown below. Discuss with your system administrator which way they feel is most appropriate. It’s important for a support engineer to see RMAN client output for the failed operation. Save the output of RMAN client operations in a text file for Veeam Support.
- Using SPOOL clause
RMAN> SPOOL LOG TO '/tmp/rman.log'; RMAN> … Actual client commands … RMAN> SPOOL LOG OFF;
(Note: https://docs.oracle.com/cd/B28359_01/backup.111/b28273/rcmsynta046.htm#RCMRF156)
- Using LOG argument when connecting to the target
$ rman TARGET / LOG=/tmp/rman.log APPEND RMAN> … Actual client commands … RMAN> EXIT
(Note: https://docs.oracle.com/database/121/BRADV/rcmcnctg.htm#BRADV8122)
- Using redirection to a file:
$ rman target / | tee -a /tmp/rman.log
4) RMAN Information
Run the following queries from an RMAN client command prompt:
RMAN> LIST BACKUP; RMAN> LIST ARCHIVELOG ALL; RMAN> SHOW ALL;
Save the output of the above queries in a text file.
5) Database Information
To provide the support engineer with overall information about the software installation on the Oracle server:
- Connect to the instance as sysdba using the sqlplus utility:
$ sqlplus / as sysdba
and run the following queries:SQL> SELECT * FROM V$VERSION; SQL> SELECT STATUS FROM V$INSTANCE; SQL> SELECT LOG_MODE FROM V$DATABASE; SQL> SELECT NAME FROM V$CONTROLFILE; SQL> SELECT USERNAME,SYSDBA FROM V$PWFILE_USERS; SQL> SHOW PARAMETER SPFILE; SQL> SHOW PARAMETER PFILE;
Save the output of the above queries in a text file for Veeam Support. - Get the following files from your Oracle database installation (ask your database administrator if you are unsure about the exact location of these files):
- For Linux/AIX:
oratab (by default it's located in /etc) inventory.xml (by default it's located in $ORACLE_BASE/oraInventory/ContentsXML) oraInst.loc (by default it's located in $ORACLE_HOME)
- For Oracle Solaris:
oratab (by default it's located in /var/opt/oracle) inventory.xml (by default it's located in $ORACLE_BASE/oraInventory/ContentsXML) oraInst.loc (by default it's located in $ORACLE_HOME)
- For Windows:
Export contents of 'HKEY_LOCAL_MACHINE\SOFTWARE\Oracle' registry key.
- For Linux/AIX:
More Information
Related Articles
- How to Collect Logs for Veeam Backup & Replication
- How to Collect Logs for Veeam Backup Enterprise Manager
- How to Locate and Collect VSS/VIX Log Files From Guest OS
- How to Collect Logs for Cases Involving Oracle
- Granular Log Collection Guide for SOBR Capacity/Archive Tier Issues
- How to Collect Logs for Veeam ONE
- How to Collect Logs for Veeam Management Pack for Microsoft System Center
- How to Collect Logs for Veeam Agent for Microsoft Windows
- How to Collect Logs for Veeam Plug-in for Microsoft SQL Server
- How to Collect Logs for Veeam Plug-in for SAP HANA
- How to Collect Logs for Veeam Plug-in for Oracle RMAN
- How to Collect Logs for Veeam Plug-in for IBM Db2
- Veeam Cloud Connect - Compiling Provider/Tenant Logs for Support Cases
- Veeam Service Provider Console – Compile and Upload Server Logs
- Veeam Service Provider Console – Compile and Upload Management Agent Logs
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.