Frequent Hyper-V errors and their troubleshooting steps

1. Configuration errors
   • Fetching Hyper-V hosts from SCVMM failed.
   • Installation failure.
   • Network not accessible or invalid credentials.
   • Failed to install the backup agent on the Hyper-V Host.
   • Failed to setup CBT driver on the Hyper-V Host.
2. Backup errors
   • Error 401 - Connecting to backup repository from Hyper-V host failed.
   • Error 403 - Not enough storage available in backup repository.
   • Error 406 - Creating VSS snapshot failed.
   • Error 410 - VM not found.
   • Error 450 - Backup Repository directory creation failed.
   • Error 451 - Recovery Checkpoint creation failed due to PowerShell Connectivity Issue.
   • Error 456 - Cannot access network share.
3. Restoration errors
   • 801 - Connecting to backup repository from Hyper-V host failed.
   • 805 - Nothing to restore.
   • 811 - VM not found. Try to perform a full restoration.
   • 812 - Backup directory not found or is empty.

Configuration errors

• Fetching Hyper-V hosts from SCVMM failed.

• Make sure that you have entered the correct user name and password of the administrator of the SCVMM machine.
• Perform the following steps.
  1. In SCVMM server, open Powershell as an Administrator and run the below commandlets

  Enable-PSRemoting -force

  Set-item wsman:\localhost\Client\TrustedHosts -value RMP_server_name -force

  Note: RMP_server_name is the name of the machine where RMP is installed.

• In RecoveryManager Plus server, open Powershell as an Administrator and run the below commandlets

Enable-PSRemoting -force

Set-item wsman:\localhost\Client\TrustedHosts -value 'SCVMM_server_name' -force

Note: SCVMM_server_name is the name of the Hyper-V server configured in the product.

• Installation failure

If you have installed the product in any machine that runs an OS version lower than Windows 8 (Windows 7 SP1, Windows 2008 R2 SP1 & Windows 2008 SP1), please make sure that you have Microsoft .NET version 4 installed in your system.

• To check if .NET Framework 4 is installed, open Command Prompt. Enter the following command

dir %WINDIR%\Microsoft.Net\Framework\v*

Check the displayed version. If the displayed version is below 4, install Microsoft .NET Framework 4 from here.

• Network not accessible or invalid credentials.

• Make sure that you have entered the correct user name and password of the the Hyper-V server.
• Check if the user account used to log on has domain administrator privileges. If not, provide the user account with administrator privileges or use an administrator’s credentials.

• Failed to install the backup agent on Hyper-V host.

• Check if the Hyper-V host is accessible from the RecoveryManager Plus server.
• Check if .NET Framework 4 is installed on the Hyper-V Host.
  • To check if .NET Framework 4 is installed, open Command Prompt. Enter the following command
  • dir %WINDIR%\Microsoft.Net\Framework\v*
  • Check the displayed version. If the displayed version is below 4, install Microsoft .NET Framework 4 from here.
• Check if the backup agent is already installed on the Hyper-V host. If it has already been installed,
  • Stop RMPHVBackup service if it is running
  • Stop HVService64 process if it is running
  • Stop HVDriverManager process if it is running
  • Delete the RMPHVBackup folder which can be found at <installed_drive>:\Program Files\ManageEngine".
  • Delete registry keys for RMPHVBackup service. Follow the steps below to delete registry keys:
    • Click Win+r. Type regedit and press Enter.
    • Delete the following keys

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{key containing RMPHVBackup}

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\{key containing RMPHVBackup}

    • Now try installing the agent again.

    Alternatively, you can also install the agent manually by following the steps listed below.

    • In the machine in which RecoveryManager Plus is installed, navigate to <Install_folder>\ManageEngine\RecoveryManagerPlus\bin and copy the file RMPHVBackup64.msi.
    • Paste the RMPHVBackup64.msi file in the Hyper-V host and open it
    • Install the file without changing the default location. The agent will now be installed in the Hyper-V host.
    • Once the agent is installed, open RecoveryManager Plus and navigate to Virtual Environment tab à Hyper-V à Configuration.
    • Click on the retry link under the 'Agent Status' column of the Hyper-V host for which you manually installed the agent.

• Failed to setup CBT driver on Hyper-V Host.

• Check if the host is already running HVDriverManager or HVService64 process. If the processes are running, stop them and retry configuring the CBT driver.
• If the issue persists, try manually installing the agent.
  1. In the machine in which RecoveryManager Plus is installed, navigate to <Install_folder>\ManageEngine\RecoveryManagerPlus\bin and copy the file RMPHVBackup64.msi.
  2. Paste the RMPHVBackup64.msi file in the Hyper-V host and open it
  3. Install the file without changing the default location. The agent will now be installed in the Hyper-V host.
  4. Once the agent is installed, open RecoveryManager Plus and navigate to Virtual Environment tab à Hyper-V à Configuration.
  5. Click on the retry link under the 'Agent Status' column of the Hyper-V host for which you manually installed the agent.

Backup errors

• Error 401: Connecting to backup repository from Hyper-V host failed.

  • Check if the host can connect to the shared repository and if the account used to configure the repository has the privilege to write to the repository.

• Error 403: Not enough storage available in backup repository.

  • Free up space from the repository and try again.

• Error 406: Failed to create VSS snapshot.

  • Make sure that the VSS service is running on the host.

  To check if the VSS service is running on the host,

  1. In the host server, press Win + r.
  2. Type services.msc and press Enter.
  3. Search for the service named Volume shadow Copy, and check the Status column to verify if the service is running.
  4. If the service is not running, click on Volume shadow Copy. In the left-pane, click the link start the service.
  • Make sure the RMPHVBackup service is running on the host.
  1. In the host server, press Win + r.
  2. Type services and press Enter.
  3. Search for the service named RMPHVBackup and check the Status column to verify if the service is running.
  4. If the service is not running, click on RMPHVBackup. In the left-pane, click the link start the service.

• Error 410: VM not found.

  This error occurs when a VM has been deleted but a backup schedule configured for the VM is still available.

  • Log in to RecoveryManager Plus as an administrator and navigate to Virtual Environment tab à Hyper-V à Configuration.
  • Click the <refresh> icon under the Actions column of the server name that has the VM.
  • Click on the number displayed under the Number of VMs field and check if the VM is listed.

• Error 450: Backup Repository directory creation failed.

  • Check if the user has privileges to write on the specified repository .If not, provide the user with required privileges and try again.

• Error 451: Recovery Checkpoint creation failed due to Powershell Connectivity Issue.

  • In the Hyper-V server, open PowerShell as an Administrator and run the below commandlets.

  Enable-PSRemoting -force

  Set-item wsman:\localhost\Client\TrustedHosts -value <RMP_server_name> -force

  Note: <RMP_server_name> is the name of the machine where RMP is installed.

  • In the machine in which RecoveryManager Plus is installed, open PowerShell as an Administrator and run the below commandlets.

  Enable-PSRemoting -force

  Set-item wsman:\localhost\Client\TrustedHosts -value <HV_server_name> -force

  Note: <HV_server_name> is the name of the Hyper-V server configured in the product.

  • After making sure that all the above commandlets have been executed without any errors, restart RecoveryManager Plus.
  • Log in to RecoveryManager Plus and navigate to Virtual Environment tab àHyper-V à configuration. Click the <Edit> icon under the action column of the corresponding Hyper-V server.
  • Provide the credentials of a local administrator of the Hyper-V host and click Add.
  • Attempt to back up the Hyper-V host. If the issue still persists, contact support at support@recoverymanagerplus.com.

• Error 456 - Cannot access network share.

  This problem occurs because the Hyper-V host does not have permission to access the network share.

  • Ensure that the Hyper-V host has permission to access the network share.

  To provide the Hyper-V host with the required privilege,

  1. Open the machine that contains the network share.
  2. Right-click on the shared folder and select Properties.
  3. Navigate to Sharing tab.
  4. Click Advanced Sharing.
  5. In the Advanced Sharing dialog, click Permissions and then click Add.
  6. Click Object Types and select Computers and then click OK.
  7. In the Enter the object names to select field, provide the name of the Hyper-V host machine and click Check Names. Select the Hyper-V host and click OK.
  8. In the Group or user names field, select the Hyper-V host. In the Permissions for field, select Full control under the Allow field and click OK.

Restoration errors

• Error 801: Connecting to the backup repository from Hyper-V host failed.

  • Check if the host can connect to the repository and if the account used to configure the repository has the privilege to read and write to the repository.

• Error 805: No files found to restore

  • The backup file is unavailable.

• Error 811: VM not found. Try to perform a full restoration.

  • Disk restorations cannot be performed on a VM which is not available.

• Error 811: VM not found. Try to perform a full restoration.

  Disk restorations cannot be performed on a VM which is not available.

  • Make sure that the VM is available or trigger a full restoration of the VM.

• Error 812: Backup directory not found or is empty.

  • The backup file is unavailable.

Copyright © 2019, ZOHO Corp. All Rights Reserved.