VeeamBR 12.2 error "Failed to create overbuild task for full oib"

[AlexLeadingEdge]

Case #07406906

Hi guys, just upgraded to VeeamBR 12.2 and now I'm seeing this error, and I have no idea what that means:

5/09/2024 9:50:45 p.m. :: Failed to create overbuild task for full oib [creation_time=29/08/2024 1:05:04 a.m.:creation_time_utc=28/08/2024 1:05:04 p.m.:alg=Full:id=d0a37260-be36-4060-bc9a-ccc2420c023c:point_id=9c05fe2a-6f27-46b5-be7b-615ca946d6d0:storage_id=abb8a83c-d159-4447-90cd-c3bf9f072f95:legacy_parent_id=00000000-0000-0000-0000-000000000000:link_id=00000000-0000-0000-0000-000000000000:original_oib_id=0aac526f-9fb9-49b0-aab5-c42173544080]:is_corrupted=True

[david.domask]

Hi AlexLeadingEdge,

Thank you for sharing the case number; Overbuild task is a process to repair inconsistent incremental points prior to merging into a full backup during retention, so it sounds like there is likely an inconsistency for that particular point.

We can see on the error stack you posted the last few bits of the string: is_corrupted=True

So regrettably, sounds like something unpleasant happened to this particular restore point. Looks like Support has advised an Active Full, which makes sense in this case. I've not heard of other reports of this with regards to 12.2, so at first blush seems to be unrelated to the upgrade.

[AlexLeadingEdge]

Thanks David,

An Active Full Backup wasn't possible, a Full Backup would have been 3TB on a 10TB (actually 9TB) drive, with the drive already being ~80% full. I have deleted all the backups from that chain and run a new Full Backup. I still have all the other backup drives we rotate through each day so no great loss.

Thanks for you help!

[jordanl17]

Hi AlexLeadingEdge,

Thank you for sharing the case number; Overbuild task is a process to repair inconsistent incremental points prior to merging into a full backup during retention, so it sounds like there is likely an inconsistency for that particular point.

We can see on the error stack you posted the last few bits of the string: is_corrupted=True

So regrettably, sounds like something unpleasant happened to this particular restore point. Looks like Support has advised an Active Full, which makes sense in this case. I've not heard of other reports of this with regards to 12.2, so at first blush seems to be unrelated to the upgrade.

I have the same error, and a similar situation with bandwidth/storage space. huge pain the delete all. and restart. do you think this error will eventually work itself out, as in, the bad retention point will be overwritten by new one in a week?

[david.domask]

Hi Jordan,

Please open a Support Case and let Veeam Support review the situation prior to taking action.

In general, this error does mean an Active Full is required for the chain that is affected. If you are using True Per-VM backup chains (default for some time), you can run Active Fulls for individual workloads (VMs) to reduce the impact of the Active Full (single machine instead of all machines in the job).

But it's best to let Support review the situation and determine how it got to this state, and if there is a means to recover from it besides an Active Full.