Troubleshooting the Instant Recovery jobs for the Agent for Hyper-V

book

Article ID: 100032755

calendar_today

Updated On:

Resolution

Issue Solution
The Instant Recovery ribbon bar is grayed out. The machine you selected for the instant recovery job is a physical server. The selected machine must be a virtual machine that was backed up using the Agent for Hyper-V.

If you select a virtual machine, then the virtual machine has not been backed up using the virtual-based backup method with Granular Recovery Technology (GRT) enabled. Select another virtual machine that has been backed up using the virtual-based backup method with GRT enabled.
I am unable to view all backup sets when configuring an Instant Recovery job. Only GRT-based backups to local, remote backup- to-disk (network B2D) and deduplication folder are supported for instant recovery.
Tape, disk cartridge, cloud based backup sets are not supported for instant recovery.
The Instant Recovery job fails with the error “Backup Exec was unable to access the backup set that is required for the instant recovery of the selected virtual machine.” Ensure that the Hyper-V server can access the Backup Exec server using either the FQDN or the hostname or the IPv4 address.
The Instant Recovery job fails with the error “0xe0009645 - Backup Exec failed to register the virtual machine.” The Hyper-V manager failed to register the instantly recovered virtual machine. Check the Virtual Machine Management Service (VMMS) events on the Hyper-V host.
The Instant Recovery job is successful but the instantly recovered virtual machine fails to power on. Ensure that the instant recovery virtual machine settings are pointing to an ISO or a DVD drive that is accessible.
The Remove a Recovered VM job completes with exceptions. If Backup Exec is unable to clean up one or more resources used by the instantly recovered virtual machine, the 'Remove a Recovered VM' job completes with exceptions. The job log may list following resources that user must clean up manually:
 
  • Folders - This folder contains the instantly recovered virtual machine files and settings that were in use when you initiated the Remove a Recovered VM job. Delete this folder. 
  • Processes - If Backup Exec is unable to connect to the Hyper-V host and you forcefully clean up the virtual machine entry from Backup Exec, some processes related to the instantly recovered virtual machine might still be running on the Hyper-V host. Manually kill such processes. 
  • Virtual machine - If Backup Exec is unable to connect to the Hyper-V host and you forcefully clean up the virtual machine entry from Backup Exec, then you must also delete the virtual machine from the Hyper-V manager.
The instantly recovered VM is not working. VM is turned on but not accessible. An instantly recovered VM is not accessible when the Hyper-V host server cannot access storage on the Backup Exec server:

Ensure that the  Backup Exec server is running.
Ensure that the network connectivity between the Backup Exec server and the Hyper-V host (where the instantly recovered VM resides) is working.

Backup Exec attempts to re-establish connection to the storage on the Backup Exec server when the server or Hyper-V machine reboots or network connectivity is restored. If Backup Exec fails to re-establish the connection:
  • Ensure that the VxLatServer process for the instantly recovered virtual machine is running on both the Backup Exec server and the Hyper-V host server.
  • If the VxLatServer process is missing on the Backup Exec server and the Hyper-V host server, try to re-launch process.
How to identify the VxLatServer process for an instantly recovered VM and restart it if found to be not running.
  1. On the Backup Exec Administration Console, on the Backup and Restore tab, double-click the All Servers server group.
  2. To list all of the instantly recovered virtual machines, in the left pane, click Recovered VMs.
  3. Enable the Process ID and Remote Process ID columns. By default, these columns are hidden.
  4. Note the following information for the instantly recovered virtual machine that you want to remove:
  • Process ID column: Refers to the id for the VxLatServer process  that should run on the Backup Exec server.
  • Remote Process ID: Refers to the id for the VxLatServer process that should run on the Hyper-V host server.
  1. Restart the Backup Exec services on the server where the VxLatServer process is not running. If the process is missing on both the Backup Exec and the Hyper-V host server, start the services on the Backup Exec server first followed by the services on the Hyper-V host server.

Issue/Introduction

If you have trouble with Hyper-V Instant Recovery jobs, review the following issues and solutions.

Additional Information

ETrack: 3879494
Powered by Wolken Software