#1 Global Leader in Data Protection & Ransomware Recovery
#1 Global Leader in Data Protection & Ransomware Recovery
BACK TO KB LIST

How to Collect Logs for Veeam Plug-in for IBM Db2

KB ID: 4554
Product: Veeam Backup & Replication | 12.1
Published: 2024-03-01
Last Modified: 2024-03-01
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 IBM Db2.
 

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 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

2) Veeam Plugin Logs on the Db2 Server

  • Collect plugin logs found in the following folder on the Db2 Server: 
    /tmp/veeam_plugin_logs
    Example:
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 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.

3) Db2 Installation Information

This step should be done on the Db2 Server.

Run the following commands and save the output as a file.

db2level
db2licm -l

4) Db2 Diagnostical Logging

This step should be done on the Db2 Server.

Gather the db2diag.log file from the affected Db2 instance.

Use the command below or ask your database administrator if you are unsure about the exact location of this file.

db2 get dbm cfg | grep -i diagpath

5) Db2 Backup history

This step should be done on the Db2 Server.

Save the output of the following command to a text file :

db2 list history backup all for <DBname>
In case of issues with archive logs processing, also capture the output of the command below: 
db2 list history archive log all for <DBname>

More Information

Related Articles
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
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.