IBM Db2 Plug-in behavior

[yanom]

Hello.
I am posting because there is something I want to check about DB2Plugin.


[Posting history]
In our system, we use DB2 and Veeam.
I am using the DB2 Plugin to get a backup of the DB2 archive log,
I am in trouble because I don't know where the backup is output.

The reason I want to check is that if I want to restore the database, I will need an archive log.
At this time, we do not know where the archive blog is located, and we do not know if it is possible to retrieve the archive log from Veeam.

I also contacted support in advance, but I posted this time because it was not resolved by the push and answer between Veeam support and DB2 support.

Veeam Case ID: #07866188 (About restoring archive logs)


[Things you want to check]
I would like to know the following two points.

1 Where is the DB2 archive log output to Veeam if I use the DB2 Plugin?
2 How do I get the DB2 archive log output above?


【Composition Information】
Deployment Server OS:Red Hat Enterprise Linux release 9.6
VBR version:12.3.2.3617
Plugins Used:/opt/veeam/VeeamPluginforDB2/libDB2Plugin.so


If you have the necessary information, check it.

Thank you.

[PetrM]

Hello and Welcome to Veeam R&D Forums!

1. The archive logs are stored next to regular database backups in Veeam repository as long as you use "include logs" parameter in the backup command. Please refer to this page for more information regarding archive log backup.
2. Maybe you can try to perform a test restore to another server to make sure that everything works smoothly? If you're interested in a specific archive log, you may ask support to check our debug logs, probably there will be some relevant info.

Thanks!

[yanom]

Hello.
Thank you for your quick answer.

Let me confirm it additionally.
Regarding 1, when I looked at the link, I understood that "archive logs are included in backups", but do archive logs only exist in backups?
Is the archive log that continues to be output not forwarded to Veeam?

[PetrM]

Hello,

I understand your question now. You should enable the LOGARCHMET1 parameter during the configuration wizard. Alternatively, you can set the LOGARCHMET2 parameter manually and specify a path to our shared library (/opt/veeam/VeeamPluginforDB2/libDB2Plugin.so) if you want to store two copies of archived logs in two different locations, with the Veeam repository being one of those locations. The plug-in will stream all archive logs to the Veeam repository, where they will be stored alongside regular backups.

Thanks!

[yanom]

Thank you for your answer.

LOGARCHMET1 parameter has already been configured with a shared library (/opt/veeam/VeeamPluginforDB2/libDB2Plugin.so).

It is possible to set LOGARCHMET2 parameters and save them in two directions,
When I checked the current status, there was an archive log that was not included in the backup.
I found out that the generation management of the archive log is not done correctly.
(Specifically, the backup doesn't seem to include the archive logs generated between backups)

Therefore, as you mentioned in "The plug-in will stream all archive logs to the Veeam repository", it seems that not all archive logs are streamed and stored in the Veeam repository.
Is this a specification?

Also, when an archive log is output on the server, a file is generated in real time.
Similar to looking at Veeam's archive blog repository, it seems that the file is not generated or saved, but is this correct behavior?