NetBackup™ Web UI Nutanix AHV Administrator's Guide
- Overview
- Managing AHV clusters
- Quick configuration checklist to protect AHV virtual machines
- Configure secure communication between the AHV cluster and NetBackup host and Nutanix Prism Central and NetBackup host
- Enable the iSCSI initiator service on windows backup host
- Install the iSCSI initiator package on Linux backup host
- Migrate Java GUI/CLI added clusters into WebUI
- Configure Nutanix AHV cluster
- Configure CHAP settings for iSCSI secure communication with AHV clusters
- About the ports that NetBackup uses to communicate with AHV
- Add or browse an AHV cluster
- Remove AHV Clusters
- Add a new Nutanix Prism Central
- Add new Prism Central server credentials
- Remove Nutanix Prism Central
- Create an intelligent VM group
- Assign permissions to the intelligent VM group
- Update the intelligent VM group
- Remove the intelligent VM group
- Set CHAP for iSCSI
- Add an AHV access host
- Remove an AHV access host
- Change resource limits for AHV resource types
- Change the autodiscovery frequency of AHV assets
- Managing credentials
- Protecting AHV virtual machines
- Things to know before you protect AHV virtual machines
- Protect AHV VMs or intelligent VM groups
- Protect AHV VMs within VPC
- Customize protection settings for an AHV asset
- Schedules and retention
- Backup options
- Prerequisite to Enable virtual machine quiescing
- Remove protection from VMs or intelligent VM groups
- View the protection status of VMs or intelligent VM groups
- Recovering AHV virtual machines
- Things to consider before you recover the AHV virtual machines
- About the pre-recovery check
- Recover an AHV virtual machine
- Recover an AHV VM within VPC
- About Nutanix AHV agentless files and folders restore
- Prerequisites for agentless files and folder recovery
- SSH key fingerprint
- Recover files and folders with Nutanix AHV agentless restore
- Recovery target options
- Pre-recovery checks for Nutanix AHV
- About Nutanix-AHV agent-based files and folders restore
- Prerequisites for agent-based files and folder recovery
- Recover files and folders with Nutanix AHV agent based restore
- Limitations
- Troubleshooting AHV operations
- API and command line options for AHV
Recover an AHV VM within VPC
The recovery of VMs on VPC comes with certain limitations listed below:
For alternate restores, the restore operation is successful if check box is selected. However, attributes like Project, category, owner information, and VPC-related information are not restored.
If there was a network configured in VM when backup was triggered and user tries alternate restore with this backup image keeping check box not selected, then restore operation fails.
If a VM had Project configured, when the backup was triggered but the project did not exist when the restore was triggered, the restore job fails.
If a VM had Category configured, when the backup was triggered but the category did not exist when the restore was triggered, the restore job fails.
If VMs user is not present in the Nutanix Prism Central server or in Project at the time of restore, then restore operation fail.
Only IP addresses with type ASSIGNED is considered for restore. Learned IP type is ignored and user must manually configure the IP after restore.
If the VM has NIC with span port enabled, then after restore this is ignored. You must manually add and configure span on the NIC with Nutanix CLI.
A VM is restored with Project, Category, Owner details, and other VPC-related attributes, if the original location restore has been performed.
An undefined behavior is observed when trying to backup/restore the VMs of a cluster which have been moved from one Prism Central to another.
A backup host with version 10.2 or later is required to backup/restore project, category and other Virtual Private Cloud (VPC) related attributes. If a backup host with version lesser than 10.2 is used, backup/restore will complete without capturing VPC related attributes if a VM is not present in VPC environment. If a VM is in VPC environment and if restore is triggered through a backup host with version lesser than 10.2, then the restore might fail.