Assuming you intend to use native Windows Server capabilities, you might want to consider Windows Server Backup (WSB) to protect the entire Hyper-V host, including its operating system and virtual machines. No third-party backup software is required.
Start by installing the Windows Server Backup feature (you can do this by using PowerShell):
Install-WindowsFeature Windows-Server-Backup
You can then open the Windows Server Backup console by running wbadmin.msc. Select Backup Schedule to configure recurring backups. For a complete host backup, select Full server. This includes the volumes required for bare-metal recovery and the data stored on the selected server volumes. Alternatively, you can select Custom and explicitly include the volumes containing the Hyper-V virtual machine configuration files and VHDX files, along with the critical volumes required for recovery. I would use Full server unless you have a specific reason to exclude data.
Configure the backup destination on a separate physical disk or a network share. Ideally, use dedicated backup storage that is not dependent on the Hyper-V host itself. A separate internal disk provides some protection against operating system or system-disk failure, but it does not protect against complete server failure. A network share or external disk provides better separation. Keep in mind that Windows Server Backup has different retention behavior depending on whether you use a dedicated backup disk or a network share.
Windows Server Backup integrates with Hyper-V through the Volume Shadow Copy Service (VSS). This allows it to back up running virtual machines without requiring you to shut them down, provided the guest operating systems and integration services support the necessary VSS operations. Application-aware consistency also depends on the guest operating system and its VSS writers. You should verify that the Hyper-V VSS writer is functioning correctly before relying on the backups.
For additional protection, I would periodically export the Hyper-V configuration information. For example, Get-VM | Export-Clixml C:\Backup\VMInventory.xml captures the VM inventory, and Get-VMSwitch | Export-Clixml C:\Backup\VMSwitches.xml captures virtual switch configuration. You should also preserve information about VLAN assignments, VM storage locations, virtual network adapters, and other host-specific settings. These exports are supplementary documentation rather than substitutes for the actual backup.
For recovery, Windows Server installation media provides access to the recovery environment. You can use System Image Recovery / Bare Metal Recovery to restore the host from a compatible Windows Server Backup image. This is particularly important if the physical server fails or the operating system becomes unrecoverable. You should test this procedure rather than assume that a successful backup job guarantees a successful recovery.
You can also use Windows Server Backup to restore individual volumes or files, while Hyper-V provides the ability to import previously exported virtual machines. This gives you several recovery options without needing to restore the entire physical server every time an individual VM has a problem.
Schedule a daily Full Server backup to dedicated backup storage, retain an additional copy on separate storage or offline media, and periodically test both individual VM restoration and bare-metal recovery.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin