Synthetics Failing

[fozz33]

Hi there.
Case #05030801.
Veeam 11.0.0.837 P20210525 Enterprise Plus

A Synthetic Full is supposed to run every weekend, but fails with the following:

Code: Select all

Failed to deserialize OibSummary. Xml: [<OibSummary><Backup Id="3a75a9e6-bee0-4774-9453-e904c40b3259" OriginalId="3a75a9e6-bee0-4774-9453-e904c40b3259" JobId="76a78548-dc45-4ce0-81c7-4b7484aaf551" JobName="Critical Servers to SOBR" PolicyName="" JobSourceType="2" JobTargetType="0" TargetType="0" JobTargetHostId="6745a759-2205-4cd2-b172-8ec8f7e60ef8" JobTargetHostProtocol="0" Platform="0" BackupPlatformId="00000000-0000-0000-0000-000000000000" BackupPolicyTag="" CreationTime="09/04/2021 19:00:19" CreationTim

The SOBR is set to remove backups older than 14-days (and I have since reduced that to 7) and also set to override if it hits 90% space used, but is doing neither.
I suspect this is becasue it would not have a viable backup chain locally if it removed the Full that it first created, and no Synthetic Fulls have been successful for this job.

Any suggestions what may be the issue?
Note that I have two other backup jobs running off this Veeam server and they also have the same issue with the Synthetics failing with the same error. They used to work but haven't since the start of September, so I am trying to figure out what changed then...maybe that's when I installed that latest (P20210525) patch.
Another reboot today has not fixed the issue so am getting desperate.

Cheers.

[HannesK]

Hello,
please continue working with support. It makes no sense to guess for the reason on a forum with this kind of error. Support will check the logs and come back to you.

Correct: the "move" policy in SOBR only works with working synthetic full backups. Move needs an "inactive backup chain"

Best regards,
Hannes

[fozz33]

I will work with support once they respond but having forum members pitch in, if they have ideas, is always a good thing.
And yep, I sent in the logs so hopefully they reveal some important info.

I will post updates here, in case others have the same issue.

[veremin]

It might be a good idea for general topics, but for others that require deeper infrastructure and log examination - support case is the fastest resolution path, cause technical issues like yours are barely addressable via forum correspondence.

Anyway, let's wait and see what support engineer finds after the debug log review.

Thanks!