Veeam Support Knowledge Base
How to Collect Logs for Veeam Plug-in for IBM Db2

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

KB ID:	4554
Product:	Veeam Backup & Replication \| 12.1 \| 12.2 \| 12.3 \| 12.3.1 \| 12.3.2 \| 13 \| 13.1
Published:	2024-03-01
Last Modified:	2026-11-03

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

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

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

2) Veeam Plugin Logs on the Db2 Server

Collect plugin logs found in the following folder on the Db2 Server, depending on its operating system:
- Linux and AIX
```
/tmp/veeam_plugin_logs
```
- Microsoft Windows (13.1 and later)
```
C:\ProgramData\Veeam\Backup\DB2PluginLogs\
```
  Each user account has its own subfolder.
Example (Linux and AIX):

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

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.

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

Cheers for trusting us with the spot in your mailbox!

Oops! Something went wrong.

Purpose

Solution

1) Veeam Plugin Logs on Veeam Servers

2) Veeam Plugin Logs on the Db2 Server

3) Db2 Installation Information

4) Db2 Diagnostical Logging

5) Db2 Backup history

More Information

Related Articles

Spelling error in text

Thank you!

Oops! Something went wrong.

You have selected too large block!

KB Feedback/Suggestion

Thank you!