KB ID : 104015
Published : Dec. 12, 2019
Created : Dec. 12, 2019
Last Modified : June 17, 2022


1) The Hyper-V Virtual Machine Management Service is not running/enabled in the owner node machine.

2) VM configured for backup is deleted/removed on the target Hyper-V Server


Cause 1:

Make sure if the Hyper-V Virtual Machine Management Service is running by following the steps below:

  • Go to services.msc in the Hyper-V host machine
  • Search for the Hyper-V Virtual Machine Management Service and find the status of the service
  • If the service is stopped or disabled, start the service and continue with the backup

When there is an issue in accessing Windows Management Instrumentation [ WMI ] of your target host, ensure the following:

Case 1: Make sure your firewall does not block any Windows Management Instrumentation function. Add the below rule into your Inbound firewall rules in your target machine to ensure the same

  1. Open control panel. Navigate to System and Security >Windows Firewall >Advanced Setting

  2. In Windows firewall with advanced security, click Inbound rules

  3. Inbound rules > click new rule and proceed to opt for the Predefined option

  4. In predefined drop-down > select ‘Windows Management Instrumentation’ rule and proceed with the default option to enable it and click finish

Case 2: Make sure the services - Windows Management Instrumentation is running on your target machine

Case 3: If you are using NAT, please make sure the WMI port is allowed in the NAT firewall

  1. If your WMI is running in a static port, then directly add the WMI port into the NAT firewall.

  2. If your WMI is running in a dynamic port, add the WMI port range into your NAT firewall. The range is from 1024 to 65535.

By default, WMI port is Dynamic. If it is not feasible, then convert the WMI port into a static port and add that static port into the firewall setting of NAT.

Steps to convert the WMI port from dynamic to static:

  1. Open Run and type ‘dcomcnfg’. Navigate the tree to My Computer → DCOM Config → Windows Management and Instrumentation, select properties of that folder

  2. Select the Endpoint tab under Windows Management and Instrumentation properties

  3. Select the Properties button for Connection-oriented TCP/IP

    1. Use static endpoint, set the port

Confirmation test: When the above-mentioned solutions are verified, perform a pre-test using WBEM utility.

  1. Open “wbemtest” in your server/client machine

  2. In the namespace text box provide Target hostname\IP : \IP\root\cimv2

     **Example:** \\\root\cimv2
  3. Provide the username and password and click on connect. Note: If the target machine you are trying to push to is a local machine, It is not required to provide username and password.

  4. If you face any issues, recheck the solution and wait until the wbem test becomes successful.

Cause 2:

Make sure the selected VM is available on the target host. If the VM configured for backup is deleted/removed on the target Hyper-VServer, then backups will fail for the VM. You need to edit the corresponding backup job and remove the deleted/removed VM from the backup configuration.

  1. To Edit and remove the VM, login to the BDRSuite Backup Server and navigate to the Backup -> List Backup Jobs page.
  2. Under the ‘Actions’ column, click on the ‘Edit’ icon alongside the corresponding backup job. Then, remove the VM and update the backup configuration.
  3. Deleted VM’s Backup Data will be retained on the backup repository based on the configured retention policy.
edit retag flag offensive close merge delete