After upgrade to VBO 6, existing backup repositories fail to upgrade

[jimmyhurr]

I have a support ticket open for this #05460074, but I wonder if anyone has any tips?

After upgrading to VBO 6.0.0.367, both my backup repositories (there are two, one for each organization feeding into a remote AWS S3 object repo) were highlighted as out of date. I rebooted the machine and right clicked the repositories and selected "Upgrade". This action failed on both with this error:

Unable to access repository: "<path to repo>\PersistentCache\repository.adb"

Checking the log file the error is:

[30.05.2022 15:02:39] 56 (2412) Failed to upgrade repository database
[30.05.2022 15:02:39] 56 (2412) Error: JetError -1504, JET_errNullInvalid, Null not valid
[30.05.2022 15:02:39] 56 (2412) Type: Veeam.Jet.JetError

[Mildur]

Hi James

Any reason why you use 6.0.0.367?
Most recent version would be 6.0.0.379 (P20220413) and has resolved issues around the repository upgrade failure.

Upgrade
Attempt to upgrade a Backup Repository that is extended to Object Storage may fail with the error:
JetError -1504, JET_errNullInvalid, Null not valid

[chris.childerhose]

This should help you resolve the issue - https://www.veeam.com/kb4293

[chris.childerhose]

Hi James

Any reason why you use 6.0.0.367?
Most recent version would be 6.0.0.379 (P20220413) and has resolved issues around the repository upgrade failure.

You are too fast here now as well Mildur

[jimmyhurr]

Ah thanks guys... I just did an automatic upgrade in the UI - this is the release it downloaded and installed....!

I'll see what support come back with - I suspect they will just say to install the patch.

[chris.childerhose]

Yeah more than likely that is what they will have you try first. Best of luck and let us know if that resolves the issue.

[jimmyhurr]

This should help you resolve the issue - https://www.veeam.com/kb4293

This fixed it Chris! Thank you!

Support sent me a private hotfix which replaced a different DLL (Veeam.Archiver.Source.dll) than the ones listed in KB4293, but it didn't work - repos still failed to upgrade. I suspect they gave me the wrong hotfix.

Anyway, I have updated the ticket and closed it.

thanks all for your help!

[HangTen]

Are the changes in KB4293 are also rolled into 6.0.0.379 (P20220413)? Can we assume if one upgrades to the latest build, the hotfix isn't needed?

[chris.childerhose]

This fixed it Chris! Thank you!

Support sent me a private hotfix which replaced a different DLL (Veeam.Archiver.Source.dll) than the ones listed in KB4293, but it didn't work - repos still failed to upgrade. I suspect they gave me the wrong hotfix.

Anyway, I have updated the ticket and closed it.

thanks all for your help!

Glad to hear this fixed it and you are up and running now.

[Mike Resseler]

@HangTen Yes, for a while now we work with cumulative patches only. In fact, a new one (Veeam speed, we are working hard these days) will come every day now (CP2) and that one will include all fixes and improvements from CP1 and also new ones

@jimmyhurr Glad to see it is fixed. I will have a look at the support call though, to figure out why the wrong dll was given. Most likely it is just a mistake made but I need to be sure that the correct patches are delivered

[Butha]

Similar issue - upgraded to latest patch from earlier Build 6, and retention on last years (2021) file doesn't clear, and esenutl defrag fails with the exact same error, even though backups go through and integrity check passes.. maybe the wrong .dll was added to latest build again?

#05627174