FLR Cannot Detect Source VM IP with Duplicate VMs on Hyper-V

Product version: 11.2

Last modified: 17 March 2026

Problem

The file-level recovery (FLR) for a Hyper-V VM fails to automatically detect the source VM IP address. During the FLR process, the system cannot identify the correct source VM, and IP detection does not complete.

Background

This issue occurs in environments where:

  • Two or more Hyper-V hosts are added to the inventory

  • A virtual machine has been replicated from one host to another

  • Both the original VM and its replica exist simultaneously

In such cases, the VMs may share identical properties:

  • Same VM name

  • Same BIOS UUID

NAKIVO Backup & Replication identifies VMs using the BIOS UUID. When multiple VMs have the same BIOS UUID, the system cannot distinguish between them. As a result:

  • Multiple matching VMs are detected

  • No single VM can be selected automatically

  • Source VM IP detection fails

This behavior is expected because the BIOS UUID remains unchanged after replication.

Solution

To proceed with the File-Level Recovery session, manually select the correct virtual machine:

  1. Initiate the File-Level Recovery wizard.

  2. On the Recovery Method tab, go to the Recovery server list and review the list of VMs.

  3. If multiple VMs are listed, manually select the correct one.

  4. On the Options tab, go to Recovery type and select Recover to custom location.

  5. Continue the wizard to complete the recovery process.