1-800-691-1991 | 9am - 8pm ET
EN

How to collect logs for cases involving Oracle

KB ID: 2374
Product: Veeam Backup & Replication 11, Veeam Backup & Replication 10, Veeam Backup & Replication 9.5, Veeam Backup & Replication 9.0, Veeam Backup & Replication 8.0
Published: 2017-11-08
Last Modified: 2021-11-17
Languages: FR

Challenge

An issue with backing up of the Oracle database server and/or removal of Oracle archived logs is suspected. Veeam Technical Support would like to gather some information from your servers and databases in order to investigate this issue.

Additional logs have to be gathered manually from the guest OS on the VM in question, because they are not captured by the Support Wizard automatically.

Solution

NOTE: If Application-Aware Image Processing is disabled, enable it and run the job again to update the log files within the guest OS.
 
The following actions need to be performed within the guest OS of the VM in question. 

NOTE:
 All Veeam Backup and Replication tasks against the guest in question must be stopped during this collection process. Otherwise the accuracy of the information will be affected.

Expand the section below that matches the OS of the server where Oracle is running.

Microsoft Windows Server
  1. Connect to the Windows machine where Oracle is running.
  2. Navigate to: %programdata%\Veeam\Backup
  3. Collect files and folders matching the following Syntax:
    • VeeamGuestHelper_ddmmyyyy.log
    • VeeamLogShipper_ddmmyyyy.log
    • OracleLib.*.log
    • %backup job name%_Oracle_Redo_Log_Backup - entire folder
  4. Open an elevated command prompt and run the following commands:

    vssadmin list writers > C:\vsswriters.txt
    vssadmin list providers > C:\vssproviders.txt

  5. Export Windows Event Logs as shown here.
  6. Connect to your instance as sysdba:

    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;
    SQL> select instance from v$thread;
    SQL> select name from v$database;

    Save output of above queries in a text file for support engineer.

  7. Collect the files from steps 2-6, and attach them to the case.
For information about attaching files to a support case, please review: https://www.veeam.com/kb4162
Linux Server
Known Issue with /tmp folder having noexec property

If the /tmp folder on the Oracle server is configured to be mounted with 'noexec', the job and credentials 'Test Now' will report success, but Oracle databases will not be backed up.

This noexec limitation is documented on KB2099.

  1. Navigate to the following directories:
    • /var/log/VeeamBackup
    • /tmp
    • /tmp/VeeamBackup

      from each folder find all files with the following filename masks:

    • VeeamOracleAgent.*.log
    • Agent.LogBackup_cli.*.log

  2. Login to the server shell with the user credentials specified in 'Guest OS credentials' field as shown here. After that issue the following commands to get basic environment information:

    cat /etc/*release
    uname -a
    env

  3. Collect information about guest components installed on your virtual machine:
    1. In case of VMware
      • Login to your Linux server
      • Run the following commands:

        # vmtoolsd -v
        # service vmtoolsd status

        or

        # systemctl status vmtoolsd

    2. In case of Hyper-V
      • Login to your Linux server
      • Run the following commands

        # lsmod | grep hv_utils
        # modinfo hv_vmbus
        # ps -ef | grep hv

      • Login to your Hyper-V host where this virtual machine is running
      • Run the following command in PowerShell (replace VM with your actual virtual machine name)

        PS> Get-VMIntegrationService -VMName "VM"

  4. Connect to your instance as sysdba from same user in shell as it was in step 2:

    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;
    SQL> select instance from v$thread;
    SQL> select name from v$database;

    Save the output of above queries in a text file for Veeam Support.

  5. Get the following files from your Oracle database installation:
    (ask your database administrator if you are not sure about the exact location of these files)
    • oratab (by default it's located in /etc)
    • inventory.xml (by default it's located in $ORACLE_BASE/oraInventory)
    • oraInst.loc (by defaults it's located in $ORACLE_HOME)

  6. Collect the logs and shell outputs from the steps above, bundle them in a compressed file, and attach them to your case.

 

For information about attaching files to a support case, please review: https://www.veeam.com/kb4162
KB ID: 2374
Product: Veeam Backup & Replication 11, Veeam Backup & Replication 10, Veeam Backup & Replication 9.5, Veeam Backup & Replication 9.0, Veeam Backup & Replication 8.0
Published: 2017-11-08
Last Modified: 2021-11-17
Languages: FR

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

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.

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 Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
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.