Due to a bug in Hyper-V 2022, the Hyper-V host will fail to register VMs that are being restored if they were using Configuration Version 5.0. Through testing, we have determined that this restore/failback issue does not occur if Application-Aware Processing was used to process the source VM that had configuration version 5.0.
Note: Configuration Version 5.0 was associated with Server 2012 R2. However, VMs with Configuration Version 5.0 may also exist on Hyper-V hosts running Server 2016 and Server 2019. Starting with Server 2022, Configuration Version 5.0 is no longer supported, and in most scenarios, the Hyper-V 2022 host will automatically upgrade those VMs to Configuration Version 8.0.
When the restore or failback operation fails to complete, the following events can be observed within the VMMS Events on the destination Server 2022 Hyper-V host:
Event 10113, Hyper-V-VMMS
Unable to parse backup metadata for component '<VM-guid>'.