Backup chain format upgrade taking forever for backups in Backblaze

[Trelor]

Hello,

I have a SOBR with a local repo and a remote to BackBlaze Repo with immutable storage. I have ~50 VMs that are being backed up with ~126 restore points both locally and at the cloud. We upgraded the backup chain-set for the copy job that we have to mirror between servers and that has intern forced us to upgrade the backup chain for the local source SOBR repo, however this process is taking a very long time. We are averaging ~20min a VM and are on 4H 45Min of the upgrade. I have done this on many other types of backup chains without issues but this SOBR -> BackBlaze is taking so long we are going to actually miss our nightly backup window. Has anyone else experienced this issue or am I just the lucky recipient of this bug.

[HannesK]

Hello,
That sounds like a technical issue. Please provide a support case ID for this issue, as requested when you click New Topic.
Without case number, the topic will eventually be deleted by moderators.

Thank you,
Hannes
PS: support can only help if you upload logs https://www.veeam.com/kb1832

[Gostev]

QA would be interested to review the logs as this is about 20 times slower than what they saw in their own upgrade testing labs.

[Trelor]

Hello,
That sounds like a technical issue. Please provide a support case ID for this issue, as requested when you click New Topic.
Without case number, the topic will eventually be deleted by moderators.

Thank you,
Hannes
PS: support can only help if you upload logs https://www.veeam.com/kb1832

I will setup a support case with the logs what logs specifically should I upload

[Trelor]

QA would be interested to review the logs as this is about 20 times slower than what they saw in their own upgrade testing labs.

Case #05910815

Backup chain upgrade took 13 hours

[HannesK]

Hello,
thank you for the logs. I forwarded the case number to QA

Best regards,
Hannes

[Gostev]

Thanks for the logs, they have found the issue and will fix this in a patch. Sounds like it triggers in some cases when upgrading a local backup chain with immutable copy in Capacity Tier.