12.3.2.4465 RMAN Plugin allocate Channel Failed

[dulgidulgi]

Hello everyone,

We upgraded our Veeam Backup & Replication server from version 12.3.2.4165 to 12.3.2.4465 as part of a security patch.
This patch also included an upgrade of the RMAN Plugin.

After applying the Veeam server patch, we proceeded to upgrade the managed RMAN plugins on the Oracle backup targets as well.
However, after the plugin upgrade, backups started failing due to channel allocation issues.

For managed plugin backups, we use an OS account named "veeam", which has been granted the necessary Oracle privileges. This setup had been working fine before the patch.
However, after the upgrade, the RMAN plugin no longer works, and all backup attempts (including full backups) fail.

The error messages are as follows:

RMAN-03009: failure of backup command on VeeamAgentChannel4 channel
ORA-19506: failed to create sequential file
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: non RMAN, but media manager or vendor specific failure
Previous session failed
Failed to create backup session
Unable to get or create backup session
Unable to execute task due to utility error

This issue occurs specifically with RMAN Plugin version 12.3.2.4465.

Additionally, even when installing the plugin in standalone mode, executing:

backup archivelog all;

through RMAN results in the same error.

All tests were performed using the "veeam" OS account, and the issue consistently occurs under this account.

As a temporary workaround, we downgraded to RMAN Plugin version 12.3.0 (standalone), and backups are working normally again.

Notably:

Using the veeam OS account, commands like rman target /, sqlplus, and manual RMAN backups (backup archivelog all;) work fine
The issue only occurs with plugin version 12.3.2.4465

This makes us wonder whether there has been a structural or behavioral change in the plugin in newer versions.

Has anyone experienced a similar issue?
Any insights or suggestions would be greatly appreciated.

Thank you.

[david.domask]

Hi dulgidulgi,

Thank you for sharing the details (including your temporary workaround), and sorry to hear about the challenges.

Please open a Support Case and allow Veeam Support time to review the behavior. The error is not expected, and will require review of the debug logs likely to find the root cause. As noted when creating a topic and in the forum rules, topics on technical issue must start with a Support Case, and once the investigation is complete if there are further questions, feel free to create a topic and reference the support case number.

So please proceed with a Support Case and share your case number here once created. Thanks.