#1 Global Leader in Data Protection & Ransomware Recovery

How to Collect Logs for Veeam Plug-in for Oracle RMAN

KB ID: 2871
Product: Veeam Backup & Replication | 10 | 11 | 12 | 12.1
Published: 2019-01-25
Last Modified: 2023-09-25
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

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

error icon

Oops! Something went wrong.

Please try again later.

Purpose

This article documents how to collect the diagnostic information needed for a support case involving the Veeam Plug-in for Oracle RMAN.

Solution

  1. Collect diagnostic information as documented in the five sections below.
  2. Combine the data into a single .zip file.
  3. 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 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:
  • 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.

  • If the backup is managed by Veeam Backup & Replication, please also collect the following logs 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 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:

  1. 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.
  2. 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.
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.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.