SureBackup Job not starting after Update to V12.1

[agrob]

Good Day

Just updated to Version 12.1 and everything worked well.

I just discovered now, that some of the scheduled Sure Backup Jobs do not start. If i start they manually, i get the following message:
"Cannot start SureBackup job to the latest restore point as some linked jobs are still running. You can use Star To option to select a previous restore point, or try again later"

The reason seems to be, that some of the VMs in the Sure Backup Job are also in a Backup Job which has SQL Server Transaction Log Processing activated. This Job is always running "<Job Name> SQL Server Transaction Log Backup". As soon as I disable this Backup Job, i can start the Sure Backup Job.
This bevavior is new and was not there in V12. I had a quick look at the release notes but have not seen any info about this... Is it a bug or am i missing a setting in the Surebackup job which needs to be changed?

p.s: if i stop the Backup Job, i can start the Sure Backup Job. Once the Sure Backup Job is (still) running, i can also enable the Backup job again and the Transaction Logs are backed up....

Thanks

[Mildur]

Hello Andre

This is a known issue which will be solved in an upcoming patch. Please open a support case to get the private hotfix now.

v12.1 Top Issues Tracker

#3: Transaction log backup jobs prevent SureBackup jobs from starting [FORUM TOPIC]
Scope: Image-level backup jobs configured to perform transaction log backups for one or more included machines.
Symptoms: SureBackup jobs cannot start due to active primary backup job.
Cause: Regression in SureBackup job pre-flight checks.
Status: Contact support for a hotfix referencing Bug ID 619612.

Best,
Fabian

[agrob]

Thanks Fabian! I'll do so

[restore-helper]

Is there a estimated time for this patch? May be before the end off february ?
As off now we postponed the migration to 12.1 because of this problem.

[agrob]

there is already a hotfix. i requested it today and already received it. i'll install it tomorrow and let you know the result

[agrob]

Installed PrivateFix_TF619987 and everything is working fine so far

[Mildur]

Hi @restore-helper
We plan to release the public patch before end of January.

@agrob
Thank you for the update.

Best,
Fabian

[Mildur]

Hello

Our public update for v12.1 which solves this issue was released today. You can update your v12.1 server to v 12.1.1 with the upgrade file provided in the following kb:
https://www.veeam.com/kb4510

A new iso is also provided for those who want to deploy a new backup server or upgrade the backup server from a previous version (10a, 11, 11a, or 12) to v12.1.

Best,
Fabian

[siranee.ja]

Hi ,
I have this problem even update to 12.1.1.56.
If I ran all of them manually , all results success but not started as schedule.
Case # 07220674 on 2024-04-12
in veeam log file Svc.VeeamBackup.log always showed

Code: Select all

[16.04.2024 14:20:10.646]   <107>   Error (3)    Unique identifier is invalid.
[16.04.2024 14:20:10.646]   <107>   Error (3)    Parameter name: id (Veeam.Backup.Common.ArgumentEmptyException)
[16.04.2024 14:20:10.646]   <107>   Error (3)       at Veeam.Backup.Model.CLeaseUid.Make(Guid id)
[16.04.2024 14:20:10.646]   <107>   Error (3)       at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
[16.04.2024 14:20:10.646]   <107>   Error (3)       at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
[16.04.2024 14:20:10.646]   <107>   Error (3)       at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
[16.04.2024 14:20:10.646]   <107>   Error (3)       at Veeam.Backup.ServiceLib.CRevivableTrackedActionManager.<>c__DisplayClass12_0.<GetLeaseIdsByActionId>b__0()
[16.04.2024 14:20:10.646]   <107>   Error (3)       at Veeam.Backup.Common.CTryCatchExecutor.Try[T](Func`1 func)

I have tried to
1. create the new application group
2. create the new Sure Job
3. ran manually the result sucess
4. set scheduling date time the result not started.

Best Regards,
Siranee

[Mildur]

Hi Siranee

Please keep working with our support team.
They will escalate the case to RnD if required.

Best,
Fabian