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
- 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
Configuring ports for the NetBackup Web Services
The NetBackup Recovery Wizard requires the proper configuration of web ports for the NetBackup Web Services on the master server. Otherwise, you cannot authorize the NetBackup plug-in to restore the virtual machines that were backed up by that master server.
The NetBackup installation process automatically runs the configurePorts script to configure NetBackup Web Services to run on any of the following sets of ports.
Table: Port sets for NetBackup Web Services
Port set | HTTPS port | Shutdown port |
|---|---|---|
First set | 8443 | 8205 |
Second set | 8553 | 8305 |
Third set | 8663 | 8405 |
If the configurePorts script does not find one of the sets free (for example 8443 and 8205), it logs an error to the following file:
Windows:
install_path\NetBackup\wmc\webserver\logs\nbwmc_configurePorts.log
UNIX and Linux:
/usr/openv/wmc/webserver/logs/nbwmc_configurePorts.log
On UNIX and Linux, the following appears on the NetBackup system console:
configurePorts: WmcPortsUpdater failed with exit status <status_code>
When this error occurs, use the following procedure on the master server to manually configure the ports. The configurePorts command is in the following location:
Windows:
install_path\NetBackup\wmc\bin\install\configurePorts
UNIX or Linux:
/usr/openv/wmc/bin/install/configurePorts
Note:
NetBackup Web Services on the master server require port 1024 or higher. Do not use a port number that is less than 1024. Ports that are less than 1024 are privileged and cannot be used with the NetBackup Web Services.
To configure ports for the NetBackup Web Services
- On the master server, enter the following to list the currently configured ports:
configurePorts -status
Example output:
Current Https Port: 8443 Current Shutdown Port: 8205
- Use the configurePorts command in the following format to re-configure a port:
configurePorts -httpsPort https_port | -shutdownPort shutdown_port
You can configure one or two ports at a time. For example, to configure the HTTPS port to 8553:
configurePorts -httpsPort 8553
Output:
Old Https Port: 8443 New Https Port: 8553
Use this command as needed to configure a set of ports for HTTPS and shutdown.
See Table: Port sets for NetBackup Web Services for a list of the port sets.
If the master server is in a clustered environment, do the following:
Make sure that the same set of ports are free on all the cluster nodes: Do step 1 on each node.
Reconfigure the ports on each node as required: Do step 2.
To override the ports that are used across all nodes, enter the following:
configurePorts - overrideCluster true
This command updates the following file on shared disk:
Windows:
install_path\NetBackup\var\global\wsl\portfileUNIX or Linux:
/usr/openv/netbackup/var/global/wsl/portfileThe NetBackup installer for
Web Servicesuses this file during installation in a clustered mode.
See Port usage for the NetBackup vSphere Client (HTML5) plug-in.