Attempt to overwrite existing non-sparse block version

[veremin]

Within open ticket you can refer to the Issue 345993 to get the hotfix for 11a version. Thanks!

[Mildur]

How long until the fix is in CU Update?
Deploying it in my infrastructure involves multiple components

[Gostev]

Probably a month or so, as there are no pressing support issues for 11a at the moment. To clarify, this issue is not specific to 11a and the majority of support cases which were opened to date on this issue are for previous product builds.

[Mildur]

Ok, thanks Anton.
I will install the hotfix tomorrow.

[s2dt]

Same here, case 05119048 .. let's see

[veremin]

Hi Sven. As far as I can see, the original issue went away, once the hotfix had been applied. Now you are experiencing different issue for which we will need additional logs and probably a case with Wasabi (cause previously similar issues were happening on their end). Thanks!

[Mildur]

Looks like a CU was released to fix this issue. I have waited to install the hotfix until now. I will give the CU a chance

Release Notes for Veeam Backup & Replication 11a Cumulative Patches - V11a P20211123

SOBR Capacity Tier: under certain circumstances, copy/offload to Capacity Tier start failing with the “Attempt to overwrite existing non-sparse block version” error.

[veremin]

Yeah, we would appreciate, if you find time to install the hotfix and share the results with us afterwards. Thanks!

[Mildur]

Hi Veremin
I will do that. I have planned to install it this afternoon.

[Mildur]

Update is installed.
I will report back in a few days if the issue is fixed.

[scottf99]

Hi. I have both the hotfix and the CU, neither installed. I get a 24hr+ turnaround in support ticket replies due to being in Australia so I thought I would try here. What is the preferred fix, hotfix or CU? My issue only started after installing 11a
Cheers
Scott

[Gostev]

Go with the CU.

[scottf99]

CU fixed this issue for me. Thanks!

[Mildur]

7 days without a single existing non-sparse block version Failure.
Works like as expected

[veremin]

Great, guys, thank for coming back and sharing the news with us; appreciated!

[that backup guy]

Hi all,

I've gotten the same error and am applying the CU now. Do I need to do anything else with this once I apply? It looks like I would get this error, Veeam would retry the offload for the affected VM, then it would succeed. Am I correct in assuming the data is fine now in S3?

Just making sure if things go boom i have an actual restore point

Thanks!

[Mildur]

Hi Backup Guy

My restore points (before and after the reported issue in the offload job) were ok in a small restore test.

After applying the cu, you don‘t need todo anything. Let the offload and everything should work out