NetBackup™ for VMware Administrator's Guide
- Introduction
- Required tasks: overview
- Configuring RBAC roles for VMware administrators
- Notes and prerequisites
- VMware vSphere privileges
- Managing VMware servers
- About VMware discovery
- Add VMware servers
- Change resource limits for VMware resource types
- Configuring backup policies for VMware
- Backup options on the VMware tab
- Exclude disks tab
- Configuring a VMware Intelligent Policy
- About the Reuse VM selection query results option
- Use Accelerator to back up virtual machines
- Configuring protection plans for VMware
- Malware scan
- Instant access
- Instant rollback
- Continuous data protection
- Backing up virtual machines
- VM recovery
- VMware agentless restore
- Restoring Individual files and folders from VMware backups
- Using NetBackup to back up Cloud Director environments
- Recover VMware Cloud Director virtual machines
- Restore virtual machines with Instant Recovery
- Protecting VMs using hardware snapshots and replication
- Best practices and more information
- Troubleshooting VMware operations
- NetBackup logging for VMware
- Snapshot error encountered (status code 156)
- Appendix A. Configuring services for NFS on Windows
- About configuring services for NFS on Windows 2012 or 2016 (NetBackup for VMware)
- Appendix B. Backups of VMware raw devices (RDM)
Prerequisites of Instant Access Build Your Own (BYO)
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
andpolicycoreutils-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.