Thank you for this insightful blogpost!
On "Optimizing Live Migration":
Do you know why Network ATC limits LM to 1, by default? This would apply to Windows Server 2025 and Azure Local.
Manage Live Migration and Mode on a per Cluster Level, instead of per node.
Sufficient to say that, starting with Windows Server 2022 or newer, customers can also specify the number of Live Migration and Mode on a cluster level. These settings will proactively override local Hyper-V settings.
How-To:
PowerShell commands aside, Windows Admin Center 2410 helps to setup cluster settings and more. A bit hidden (Add cluster object >connect > options).
Performance issue when using RCT /CBT, solved.
Customers of Windows Server with Hyper-V 2019, 2022 and Azure Local 22H2 are likely affected by performance issues, when using a Backup Software and RCT / CBT.
This technology helps to drastically speed up backups and recoveries. If a bit in a TB file got changed RCT would only Backup or Restore the changed block in a differential or incremental, instead of the whole blocks of that file.
Using RCT has caused an issue which impacted performance of the VM over time, unless a LiveMigration moved the VM, to remediate the problem, temporarily.
Good news, Microsoft and Veeam have found the root cause and offering a solution.
Other BCDR vendors supporting RCT (CBT), like CommVault, Macrium Reflect etc. should be remediated from this performance degradation, likewise.
More information and guidance:
https://forums.veeam.com/posting.php?mode=quote&p=539270 /
https://www.veeam.com/kb4717
