Description

• Requirements for instant recovery of a VMware virtual machine

1. ​Backup Exec Server:
   • Windows Server 2012 or later
   • Backup Exec 15 Feature Pack 5, Backup Exec 16 or later
   • Windows feature ‘Server for NFS’ must be installed on the Backup Exec Server
   • Licensed Agent for VMware and Hyper-V
   • Instant recovery is not supported in a clustered Backup Exec environment
2. Destination VMware Server

• Must be vSphere 5.1 or later
• Storage vMotion is recommended to migrate/move the instantly recovered virtual machine to another server/storage. If Storage vMotion is not licensed, the virtual machine will have to be powered off prior to migration.

• Requirements for instant recovery of a Hyper-V virtual machine

1. ​Backup Exec Server:
   • Windows Server 2008 SP2 or later
   • Backup Exec 15 Feature Pack 5, Backup Exec 16 or later
   • Licensed Agent for VMware and Hyper-V
   • Instant recovery is not supported in a clustered Backup Exec environment
2. Destination Hyper-V Server

• Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2
• Agent for Windows version Backup Exec 15 Feature Pack 5, Backup Exec 16 or later

In an environment where one or more Backup Exec servers are managed by a Central Administration Server (CAS):

1. It is recommended to run the Instant Recovery operation from the Backup Exec server that actually ran the backup job. 

2. In a rolling upgrade environment where not all Backup Exec servers are upgraded to the same version as CAS, backup sets residing on older managed Backup Exec servers will be filtered out in the Recover VM wizard. In some scenarios where the devices 
     are shared between multiple Backup Exec servers the sets may not get filtered. In this case, run the job on the CAS or the Backup Exec server that is running the same version as CAS.

Note:
For other requirements, please refer to the following on Administrator's Guide.

• Requirements for instant recovery of a VMware virtual machine
• Requirements for instant recovery of a Hyper-V virtual machine