Tape backup fails as Source backup starts Since upgrade to v12

[goldz35]

Hi, wondering if anyone knows of a fix for the following issue since upgrading from v11 to v12. I have a support case with Veeam currently (06080047) but they were not quite sure if there is a fix for this.

Our backup to tape jobs require a few days to finish due to requiring 2-3 tape changes. As this takes a considerable amount of time they are generally end up set to "Waiting for Tape" overnight at which the Source backup kicks off and fails the Tape Backup. The option in tapes to prevent source from terminating the tape backup is not an option for our environment as the daily backups may not run for 2-3 days if that setting is enabled.

Current version is 12.0.0.1420 P20230412

This was not an issue with v11 because the Waiting for Tape would not be interrupted by the source backup when it started every night.

I don't believe there is a rollback option too as the database itself was upgraded during the upgrade.

Any help would be appreciated. Thanks

[Mildur]

Hi Gold

Rollbacks are not supported. The new backup files from v12 wouldn't be compatible with v11.
Can you please try the following registry key?

post486632.html#p486632

Code: Select all

Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
Name: TapeBackupLocksResolution
Type: DWORD
Value: 0

Best,
Fabian

[goldz35]

Hi Fabian,

That worked perfectly. Thank you very much!

[Seb.pythoud]

Hi Gold

Rollbacks are not supported. The new backup files from v12 wouldn't be compatible with v11.
Can you please try the following registry key?

post486632.html#p486632

Code: Select all

Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
Name: TapeBackupLocksResolution
Type: DWORD
Value: 0

Best,
Fabian

Hi Fabien,
Is this key still needed in current version (12.3.2.4165) when option « Prevent this job from being interrupted by source backup jobs » is enabled ?
I'm trying to find a way to make my tape jobs shorter (by avoiding the tape job to be paused/canceled/retried with this « Prevent this job from being interrupted by source backup jobs » option, without having my primary jobs postponed).
thx.

Seb

[david.domask]

Hi Seb.pythoud,

The config parameter and the option « Prevent this job from being interrupted by source backup jobs » have slightly different purposes.

The config parameter adjust how the tape job will approach backing up backups that are True Per Machine backups. (Backups with separate metadata for each workload processed in the job). Without the config parameter, if a primary job is working with some of the backups, the tape job will queue until the primary job finishes processing all of its workloads.

The option Prevent this job from being interrupted by source backup jobs determines how the Tape job will behave if one of the source jobs needs to lock the backup files. With the option disabled, the Tape job will surrender its lock to the primary job and the tape job will end with an appropriate error telling as such. With the option enabled, the Tape job is allowed to retain its locks on the backup files, and the primary job will queue any workloads it cannot lock and move on to other tasks (if available). In ideal world, this option doesn't impact your primary jobs as they'll just move on to other tasks.

[Seb.pythoud]

hi David.

To be sure to understand, is it correct to say : "with True Per Machine backups and « Prevent this job from being interrupted by source backup jobs » option enabled, only VM that are currently backed up to tape (2 VMs if 2 drives are used, for exemple) will have their primary backup delayed until tape job release its locks, and all other VMs will backup normally" ?