NetBackup™ for Nutanix AHV Administrator's Guide
- Overview
- RBAC roles for the Nutanix AHV administrator
- RBAC roles for the Nutanix AHV administrator
- Assign both the Default VMware Administrator and Default AHV Administrator roles to a user
- Create a custom role for all Nutanix AHV permissions and additional VMware asset permissions
- Create a custom role for all VMware permissions and additional Nutanix AHV asset permissions
- 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 the web UI
- Prerequisites to configure Nutanix AHV cluster
- About support for Nutanix segmented iSCSI network
- 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
- Scan for malware
- Managing credentials
- Instant access
- Protecting AHV virtual machines
- Things to know before you protect AHV virtual machines
- Protect AHV VMs or intelligent VM groups using Protection plan
- Backup AHV VMs or intelligent groups using Policy
- Protect AHV VMs within VPC
- Customize protection settings for an AHV asset
- Modify policy 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
- Protecting Nutanix Cloud Clusters (NC2)
- Troubleshooting AHV operations
- API and command line options for AHV
Prerequisites of Instant Access Build Your Own (BYO)
Prerequisites (fresh install and upgrade):
The BYO storage server with Red Hat Enterprise Linux 7.6 and later, same as the NetBackup Appliance operating system version.
The BYO storage server with docker/podman installed.
The docker/podman version must be same as the one in the corresponding official RHEL version release. You need to install it from the corresponding RHEL yum source (RHEL extra).
The docker/podman application is included in the environment path.
The BYO storage server with NFS service installed.
The BYO storage server with NGINX version installed.
The NGINX version must be same as the one in the corresponding official RHEL version release. You need to install it from the corresponding RHEL yum source (epel).
Ensure that the policycoreutils and policycoreutils-python packages are installed from the same RHEL yum source (RHEL server) and then run the following commands:
semanage port -a -t http_port_t -p tcp 10087
setsebool -P httpd_can_network_connect 1
Ensure that the /mnt folder on the storage server is not mounted by any mount points directly. Mount points should be mounted to its subfolders.
Enable the logrotate permission in selinux using the following command:
semanage permissive -a logrotate_t
For BYO, docker/podman container is used to browse VMDK files. Data related to the container is stored at the following location:
/var/lib/and requires minimum 20 GB free space.