V12.1 surebackup

[SnakeSK]

Case 07040009. We have one vm backup job configured to back up sql logs periodically. After upgrading the v12.1, we can no longer run the surebackup job containing the vms because v12.1 sees the job as active and not finished, is this expected behaviour? Why was this changed? Because it pretty much locks up our surebackup and backup compliance.

When i disable the backup job, wait till the sql log backup job stops, i can run the surebackup job again.

[Dima P.]

Hello SnakeSK,

Checking the case details, stay tuned.

[Dima P.]

We were able to reproduce the behavior, investigating the root cause now. I'll update this thread once I got more details.

[TheLittleOne]

Hi,

I have the same problem, is there an update on this case?

Edit: sorry I found Bug ID 619612 and contacted support

Thanks

[SnakeSK]

Hotfix breaks the functionality of SureBackup agent backups, so use with caution

[Dima P.]

Hotfix breaks the functionality of SureBackup agent backups, so use with caution

I've check both Veeam B&R and Veeam One cases and found the mentioning of the issues of data collection from Veeam One, but no issues related to agent-based backup. Can you please confirm that these are resolved and you do not see any side effects caused by this private fix? Thank you!

[SnakeSK]

We are still seeing it, scripts dont run at all. Even after hotfix that I mentioned, there was issue regarding the bustype or something.

[Dima P.]

SnakeSK,

The investigation is still in progress with the case 619612 or you have another case ID I can look at? Thank you and Happy New Year!