Failed to upgrade capacity tier to a new format

[sarapinho]

Hey guys,

Is there any way to do this upgrade manually? In my case after updating vbr to v12 the offload returns with failed upgrade index.


02.03.2023 17:32:10.272] <20> Error        Capacity tier storage index is out of sync. (Veeam.Backup.Common.CCppComponentException)
[02.03.2023 17:32:10.272] <20> Error            in c++: Failed to enum
[02.03.2023 17:32:10.272] <20> Error            in c++: Failed to upgrade capacity tier to a new format.
[02.03.2023 17:32:10.272] <20> Error            in c++: Failed to process method 'ArchRepo.UpgradeToV2'

Case # 05865095

Thanks

[Mildur]

Hi Amauri

Please keep working with your current support engineer.
You can ask this question directly in the case. If we do something parallel over the forum,
it can interfere with the analysis in the case.

If you want to escalate the case, please also use our talk to a manager feature:
https://www.veeam.com/kb2320


Best,
Fabian

[sarapinho]

Hi Fabian

Yes, we escalate the case.

But so far we have had no further response!

Thanks

[Mildur]

Hello Amauri

Just saw in the case notes, that you use Zadara object storage.
We have some other cases with issues related to Zadara object storage. I cannot say if your case is related to the issues other are seeing, but our RnD is investigating this issues.

Best,
Fabian

[sarapinho]

Hi Fabian,

Thanks for the feedback, for more tests I upgraded another VBR with less backup data that also has the zadara object storage and is apparently working normally.

Thanks

[carlos.costa]

Hi Amauri,

The another VBR mentioned, are working with Zadara with object lock bucket?

Regards,
Carlos

[sarapinho]

Hello Carlos,

Yes, it is working in an environment with much less volume.

Veeam support requested a non-immutable bucket and also patched Veeam.

Thanks
Amauri

[alain.deguille]

Hello,

I have the same problem.
What was the solution please ?

[Mildur]

Hi Alsin

Without a case we cannot make sure you are affected by the same issue.
Please make sure you have the latest build installed.
https://www.veeam.com/kb2680

If it‘s still not working, please open a support case and let me know the case number.

Thank you very much,
Fabian