Backup Logs Periodically Is Not Supported for More Than One Database Engine per Job Object (Veeam Agents and Plug-ins)

When saving Guest Processing settings for a Veeam Agents backup job with periodic transaction log backup enabled for more than one database engine (Microsoft SQL Server, Oracle, or PostgreSQL) on the same job object, the following error occurs:

Concurrent transaction log backup is not supported.

Alternatively, when the same configuration is applied to a Veeam plug-in backup job (e.g., Veeam Backup for Nutanix AHV, Proxmox VE, or another supported hypervisor plug-in), no error is displayed, but none of the configured database engines' transaction logs are backed up for that job object.

This applies to the Backup logs periodically option on the SQL tab of Processing Settings, and the Back up logs every option on the Oracle and PostgreSQL tabs. A job object can be an individual machine, or a container such as a Prism Central category, protection group, pool, or tag.

This issue occurs because Veeam Agents and Veeam plug-in backup jobs create one transaction log backup job per machine, and only one database engine's periodic log backup can be active per job object. This behavior is by design and is documented for Veeam Agents in the Veeam Agent for Microsoft Windows and Veeam Agent for Linux user guides. For Veeam Agents jobs, this restriction is enforced when the Guest Processing settings are saved. For Veeam plug-in jobs, this restriction is not currently enforced when the settings are saved; enabling periodic log backup for more than one database engine on the same job object results in none of the configured engines' transaction logs being backed up when the job runs. Veeam Backup & Replication jobs for VMware virtual machines use a different architecture and are not affected by this limitation.