One way to have Veeam tracking the IDs of backed up VMs is SCVMM or having all instances as roles within the failover cluster manager.
I have to configure an instance / role to absolutely NOT restart after a failure of a node. The infos I duckduckwent left me somewhat unclear whether it's sufficient to define the policies accordingly or have to define "no restart" of the role (VM) as configurable in the Hyper-v Management console or FOCM.
Can you please describe what Veeam do in this situation? Do you do VM Replication or Backup with Veeam. Do you mean that after Veeam restore/failover the VM should not start?
Can you maybe explain why so that we can understand it better?
Veeam is in play because a moved "non-clustered" VM will not be successfully backed up - besides SCVMM or clusterd machine. So it's a side effect of using Veeam.
I have to be sure that the back ups will go on uninterrupted. I would put the VMs into clustered HA mode, but have to be sure that in case of a node failure, the instance won't be moved/started to another node and run from there.
I thought a fellow user of Veeam might have run into a similar problem - and I have to admit: it's not a Veeam-only problem.
You have configured a Failover Cluster for Hyper-V with a Clustered Shared Volume or a SMB3 as datastore volume for the VMs.
You will add the Failover Cluster as Hyper-V Managemed Server object to Veeam.
Then you create backups for the VMs.
In that situation we do not do any kind of live migrations for the VM.
The problem ist that in Germany there is a "Datev" - they are very, very finnacky what and when they support their application (you may have heard of'em).
I absolutely want to (re)start their server only "supervised".
Your two links in addition with some other findings will help me to set it up.
BTW: they still won't support instances that were backuped with their sql running....
Thanks for the feeback.
Yes I know Datev very well.
Maybe the last sentence is not correct anymore? I think it would be good to check with them for this specific point.
left me somewhat unclear whether it's sufficient to define the policies accordingly or have to define "no restart" of the role (VM) as configurable in the Hyper-v Management console or FOCM.