Hyper-V Backup Copy complains that Hyper-V cluster is down.

[srdegeus]

This is still update 3a

We are in the middle of moving our 'data center' and are making final backups of the VMs and run the offsite copy.
We ran the Backup Jobs after shutting down the VMs and after successful completion we stopped the cluster.

Now when we run the 'Sync Now' on the copy jobs, we get tasks failures because:
2019-02-08 14:06:52 :: Task failed. Failed to expand object <VMname>. Details: Host '<cluster name>' either not a cluster or cluster services is unavailable.

Why would the Backup Copy Job try to contact the cluster? Shouldn't the Backup Copy Job just copy the latest recovery point from the backup repository.
Is this a design flaw or am I missing something crucial here?

[Rick.Vanover]

Hi there srdegeus, the Backup Copy Job logic does need to verify the source object exists before performing the downstream task to make a restore point at other storage. For one, it verifies it exists so the "restore to original location" logic can be handled - as an item may have moved between the time of backup and backup copy - and this logic will give a more seamless restore experience.

You'll see in the user guide this line " The backup copying process does not affect virtual and physical infrastructure resources, does not require creation of additional VM checkpoints or VSS snapshots and does not produce load on machines whose backups are copied."

But this means it does not affect it - meaning does not read/checkpoint, but does query. https://helpcenter.veeam.com/docs/backu ... l?ver=95u4

[srdegeus]

Hi Rick.Vanover,

Thanks for the explanation that it needs to query the original host. We will make sure that the cluster is still up after the backup is complete, so that the copy job runs without warnings.