Veritas NetBackup™ Plug-in for VMware vSphere Client (HTML5) Guide
- Introduction and notes
- Installing the NetBackup plug-in for vSphere Client (HTML5)
- Requirements for the NetBackup plug-in for vSphere Client (HTML5)
- Using consistent vCenter naming with the NetBackup plug-in for vSphere Client (HTML5)
- vCenter privileges for managing NetBackup plug-in installation
- Notes on using the vSphere Client (HTML5) plug-in in a VMware Platform Services Controller (PSC) environment
- Installing the NetBackup plug-in for vSphere Client (HTML5)
- Upgrading the NetBackup plug-in for vSphere Client (HTML5)
- Uninstalling the NetBackup plug-in for vSphere Client (HTML5)
- Configuration overview for the NetBackup Recovery and Instant Recovery Wizards
- Configuring ports for the NetBackup Web Services
- Port usage for the NetBackup vSphere Client (HTML5) plug-in
- Creating an authentication token for the NetBackup plug-in for vSphere Client (HTML5)
- Authorizing the NetBackup vSphere Client (HTML5) plug-in to restore virtual machines
- Configuring the plug-in for an external certificate
- Reconfiguring the plug-in for a NetBackup CA-signed certificate
- Setting vCenter privileges for recovering virtual machines
- Adding or deleting an additional host name or IP address for an authentication token
- Revoking an authorization token
- Renewing an authorization token
- Listing all current authentication tokens
- Permissions on the NetBackup plug-in authentication token file may need to be changed
- Excluding virtual disks from the backup
- Monitoring backup status
- Restoring virtual machines
- Troubleshooting
- The message NoPermission appears during plug-in installation
- Reducing the load time for the NetBackup plug-in for vSphere Client (HTML5)
- A NetBackup master server is not available in the master server list of the Instant Recovery Wizard
- The NetBackup plug-in for vSphere Client (HTML5) does not find any backup images in the listed events
- The NetBackup Recovery wizard for vSphere Client (HTML5) does not find a particular backup image
- Mismatch in vCenter server name (uppercase vs. lowercase letters) causes the VMware connectivity test to fail
- Instant recovery operation is not complete due to NFS mount limit exceed
- Instant recovery-ready backup images are not available for selection
- The vCenter server and NetBackup master server names are not available for search
- Preferred Instant recovery destination options are not saved
- Virtual machine display name conflicts are not shown before the pre-recovery check
- Reasons for failure of pre-recovery checks
- Too much time taken to populate the list of NetBackup master servers
- The NetBackup plug-in is not shown in the vSphere Client (HTML5) interface even after registration
- The correct NetBackup master server does not show up for selection for a given vCenter server on the Instant recovery wizard
- Troubleshooting master server communication failures in the plug-in's Recovery Portal
- Appendix A. Instant recovery events and best practices
- Appendix B. Installing the vSphere Client (HTML5) plug-in from a NetBackup media server and plug-in package host
Notes on using the vSphere Client (HTML5) plug-in in a VMware Platform Services Controller (PSC) environment
For the vCenter servers that a VMware Platform Services Controller (PSC) manages, note the following about the NetBackup plug-in:
The plug-in only needs to be installed on one of the vCenter servers. The installed plug-in is accessible to all the vCenter servers under the PSC.
You must register the NetBackup master server on each vCenter server where virtual machines are to be restored.
See Authorizing the NetBackup vSphere Client (HTML5) plug-in to restore virtual machines.
Backups of the virtual machines that reside on vCenter servers under the PSC can be restored to any vCenter under the PSC. Backups of the virtual machines that reside on vCenter servers outside of the PSC cannot be restored to vCenter servers under the PSC.
For example: A VM was backed up on vCenter 1. To restore that VM to vCenter 2, both vCenters need to be under the same PSC. In this case, the NetBackup master server needs credentials at least for vCenter 2.