Exploring v13 upgrade again - previous attempt had major problems

[matthewcassell]

Back in Dec I attempted to upgrade our v12 environment to v13. At first most things seemed like the were going fine, however we ran into an issue where backup merging was taking a significant amount of time, to the point that we had to revert back to using v12 since our backups could not complete within 24 hours. All of our backups are directed to an Object First OOTBI appliance. At the time it was recommended by Veeam that we switch our backups from forever forward incremental to running full backups weekly to reduce the amount of data merging that would happen (we keep 30 days on premise). This would cause a sharp increase in storage consumption, to the point that we would need to add another appliance to our environment.

We have never had a problem with the merging on v12, but since that is soon going to be end of support we will have no choice but to upgrade to v13. I was wondering if this performance problem might have been fixed in the latest updates as we are hesitant to go through this again. Or if I was to kick off a single manual full after the upgrade should I expect the issue to not reoccur? I suspect the merging that is happening in the Object Storage is only the metadata and I'm guessing that in v13 Veeam changed the way the metadata is stored or written or something along those lines causing the delays as it tried to update the metadata from v12 format to v13.

Has anyone else had any experience with this scenario? Just looking for some user experience here as a rollback is not fun.

Thanks,

Matt

[david.domask]

Hi Matt,

Sorry to hear you had challenges on v13.

Can you please share the previous case number? You are correct there is no actual merging with Object Storage, it's all metadata operations since you can't really merge two objects like with block storage (especially with immutability)

I'm not aware of any specific issue on 13.0 that matches this description, but can review the case and hopefully can comment a bit more on what specifically was going slow.