Veeam Cookbook
The Veeam Cookbook Series
A simple step by step no frills approach to achieving your goal
Recipe: Performing Instant Recovery of Workloads to Nutanix AHV
Expected deliverables:
A VM started in a Nutanix AHV cluster directly from a Veeam backup with Instant Recovery.
Time to complete: 5 minutes
Ingredients:
- A Nutanix AHV cluster added to the backup infrastructure, running Nutanix AOS 6.0 or later.
- At least one Restore Point of the virtual machines to be recovered.
Assumptions:
You have a Veeam Backup and Replication server installed.
Method:
- Open the Veeam Backup & Replication Console and select Home on the bottom left menu.
- Select Backups in the inventory pane, expand the necessary backup job, right-click the VM you want to restore and select Instant recovery.
- In the wizard, select Nutanix AHV as the target platform and click Next.
- At the Machines step, you can choose to restore multiple VMs at a time. To do that, click Add -> From backup…. Choose the desired VMs from the backups and click Add.
- Select a restore point for every VM to be recovered or keep the default.
- Click Next.
- At the Restore Mode step, specify a destination for VM recovery and click Next.
- At the Cluster step, specify the cluster where you want to locate the recovered VMs, by selecting the VM and clicking in Cluster.
- At the Storage Container step, specify storage container where virtual disks of the recovered VM will be stored, by selecting the VM and clicking in Container.
- At the Name step you can change the name of each restored VM.
- At the Network step, choose a network to which the recovered VM will be connected, by selecting the necessary VMs and clicking Network.
- In the Reason step, enter a reason for performing the Instant Recovery and click Next..
- In the Summary step, choose if the target VMs should be powered on and connected to the network, and then click Finish.
Important: After the VMs have been successfully recovered, you must finalize the process. For this, test the recovered VMs and decide whether to migrate them to production environment or stop publishing
Links to Resources: