Veritas NetBackup™ Plug-in for VMware vSphere Web Client Guide
- Introduction and notes
- Installing the NetBackup plug-in for vSphere Web Client
- Requirements for the NetBackup plug-in for vSphere Web Client
- Using consistent vCenter naming with the NetBackup plug-in for vSphere Web Client
- vCenter privileges for managing NetBackup plug-in installation
- Notes on using the plug-in in a VMware Platform Services Controller (PSC) environment
- Installing the NetBackup plug-in for vSphere Web Client
- Configuring the plug-in for an external certificate
- Reconfiguring the plug-in for a NetBackup CA-signed certificate
- Upgrading the NetBackup plug-in for vSphere Web Client
- Disabling the NetBackup plug-in for vSphere Web Client
- Uninstalling the NetBackup plug-in for vSphere Web Client
- Configuration overview for the NetBackup Recovery and Instant Recovery Wizards
- Configuring ports for the NetBackup legacy Web Services
- Port usage for the NetBackup vSphere Web Client Plug-in
- Creating an authentication token for the NetBackup plug-in for vSphere Web Client
- Authorizing the NetBackup plug-in to restore virtual machines
- 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 Web Client
- A NetBackup master server is not available in the master server list when searching for VMs for instant recovery
- The NetBackup plug-in for vSphere Web Client does not find any backup images in the listed events
- The NetBackup Recovery Wizard for vSphere Web Client does not find a particular backup image
- Mismatch in vCenter server name (uppercase vs. lowercase letters) causes the VMware connectivity test to fail
- IR 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 IR-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 Web Client interface even after registration
- Correct NetBackup master server does not show up for selection for a given vCenter server on the IR wizard
- Error stack displayed in the NetBackup plug-in for vSphere Web Client
- Troubleshooting master server communication failures in the plug-in's Recovery Portal
- Appendix A. Instant recovery operations
- Appendix B. Installing the vSphere Web Client plug-in from a NetBackup media server and plug-in package host
Permissions on the NetBackup plug-in authentication token file may need to be changed
To allow the NetBackup plug-in to restore VMs, the NetBackup administrator must generate an authentication token on the NetBackup master server. NetBackup creates the token in a compressed file; the file must be sent to the administrator of the vCenter server where the plug-in is installed.
When the virtualization administrator uses the compressed file to authorize the plug-in to restore VMs, the token file is opened and left uncompressed. In either of the following cases, the uncompressed file may not have the same permissions that it had when the NetBackup administrator created the token:
On the Linux vCenter Server Appliance, the umask is set to 0.
VMware vSphere on Windows is installed in a location other than C:\Program Files.
In either case, you may need to adjust the token file's permissions to conform to your NetBackup security settings.
The uncompressed token file is in the following location on the vCenter server:
On a Linux vCenter Server Appliance: /storage/vsphere-client/netbackup
On a Windows vCenter server: C:\ProgramData\VMware\vSphere Web Client\netbackup