Modifying a failover cluster backup job via PS fails, once SQL log-shipping is used

[mdiver]

We observe a strange behavior when programatically creating or adjusting agent backup jobs (e.g. Windows failover cluster within VMs or physical).
Once SQL log-shipping is enabled for the workload, the PS script to manipulated the job fails with the following error logged:

Code: Select all

[21.06.2021 08:46:20] <16> Error The specified computer backup job is invalid.
[21.06.2021 08:46:20] <16> Error Destination:
[21.06.2021 08:46:20] <16> Error Move all backup files to the new backup repository first. 

Just as if the backup chain was deleted. Before enabling log shipping it worked es expected.
This happens ONLY once backup files are present. So VBR seems to look for something it expects within the chain that is not there.

We opened and case (#04872488) and Veeam support could reproduce the problem.
We learned it to be a confirmed bug (329853).

Did anyone else see this behavior? Did anyone find a viable workaround to manipulate jobs with log-shipping enabled?

Thanks,
Mike

[oleg.feoktistov]

Hi,

Is your agent backup job targeted to a SOBR? Because the bug you shared is not relevant to log shipping jobs being enabled/disabled.
It points to the fact that when editing such job via Powershell VBR cannot find metadata on one of SOBR extents if agent child backups are residing on distinct extents. From what I see in your support case, it might fall under bug's scope, but I'm not sure if you are using SOBR as a target. The workaround here is, unfortunately, a non-programmatic. That is, to edit such jobs through the UI.

Best regards,
Oleg