nmdange wrote: What I do (and you might consider) is run Veeam itself within a VM and the Hyper-V host acts only as a backup repository and off-host proxy. In that case, taking a backup of the physical host is not particularly important since it would not take that much to just reinstall the OS.
That is my (client's) setup: Veeam in a VM on this host to which I have recently added a >64TB volume to be an additional Veeam repository.
Obviously I want/need to keep backing up the Veeam VM. If the additional repository is >64TB all VB&R VM backups fail, and so does the VEB backup of the host (unless I back up only the OS drive - if I back up OS and system recovery drives, VEB fails). NB these failing backups do not use the new >64TB repository, and all work if the >64TB volume is shrunk to <64TB.
This being a relatively small client, we don't want to have to buy a separate physical server just to handle the >64TB repository.