

Creating Plans to Protect Data › How to Create and Manage an Instant Virtual Machine › Review the Prerequisites for an Instant Virtual Machine
Review the Prerequisites for an Instant Virtual Machine
Complete the following prerequisites before creating an Instant VM:
- Verify that you have at least one Arcserve UDP backup.
- Verify that the Arcserve UDP Agents are already installed on the Recovery Server.
- Verify that the NFS feature is installed on the Recovery Server, if the destination hypervisor is a VMware vCenter/ESX(i) server.
- Verify that the operating system of the Recovery Server is 64-bit Windows Server 2008 R2 or later.
- Verify that the Recovery Server has enough space for the Instant VM.
Note: Machine can boot up. NIC(s) are configured according to the user input on UI.
Consideration
- The Migrate InstantVM between nodes feature is not supported when an Instant VM is started in a Hyper-V cluster.
- When you create an Instant VM from a Linux agent backup, the settings of a virtual machine created by Instant VM cannot be modified using a vSphere client. You must use the vSphere web client to modify the virtual machine settings.
- If the number of NFS datastore reaches the maximum number of NFS mounts on an ESXi/ESX host and you create an Instant VM, then Arcserve UDP fails to create the NFS datastore. To increase the maximum number of NFS mounts on the ESXi/ESX host, see the VMware KB article.
- If recovery point is from agentless backup, and destination hypervisor is vsphere ESX/VC, the NFS server is required on the Linux Backup Server machine.
- If target hypervisor is MS Hyper-V, command net must be available on the Linux Backup Server. This command may be installed by samba client packages.
- The virtual machine does not work in the following situations:
- Recovery server reboots.
- Recovery server crashes.
- The network connection between recovery server and backup destination (Data store or shared folder) disconnects.
Copyright © 2016 .
All rights reserved.
 
|
|