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
Configuring the plug-in for an external certificate
The plug-in communicates with the NetBackup master server securely by means of certificate-based authentication. By default, the master server uses NetBackup CA-signed certificates. As an alternative, the master server can be configured to use an externally issued certificate. In that case, use the following procedure to configure the plug-in for the external certificate.
Configure the plug-in for an external certificate
- Enter the following command on the master server:
Windows
install_path\NetBackup\wmc\bin\install\configureCertsForPlugins.bat -registerExternalCert -certPath "path_to_external_certificate_file" -privateKeyPath "path_to_certificate_key_file" -trustStorePath "path_to_ca_certificate_file"
UNIX, Linux
/usr/openv/wmc/bin/install/configureCertsForPlugins -registerExternalCert -certPath "path_to_external_certificate_file" -privateKeyPath "path_to_certificate_key_file" -trustStorePath "path_to_ca_certificate_file"
For example:
configureCertsForPlugins -registerExternalCert -certPath "c:\server.pem" -privateKeyPath "c:\key.pem" -trustStorePath "c:\intermediateOrRootCA.pem"
This command configures the plug-in to use the external certificate by importing the certificate into the keystore on the master server. The command options are as follows:
-certPath: Specifies the path to the certificate for the web server. This file should have a single certificate in PEM format.
-privateKeyPath: Specifies the path to the private key for the web server certificate.
-trustStorePath: Specifies the path to the certificate of the intermediate or root certification authority that has issued the web server certificate. This file should have a single certificate in PEM format. The subject of this certificate should match the issuer of the web server certificate.
For further information on external certificates, see the NetBackup Security and Encryption Guide.
- Restart the NetBackup Web Management Console service on the master server.
In the Activity Monitor of the NetBackup Administration Console: Click the Daemons tab, right-click the service, and click Stop Daemon. When the service has stopped, click Start Daemon.
- Renew the authentication token on the master server:
See Renewing an authorization token.
Note:
Perform this step for each plug-in that needs to communicate with the master server.
- On the plug-in, remove the existing master server and then add the master server that now has the renewed token:
See Authorizing the NetBackup plug-in to restore virtual machines.
If you use external-CA signed certificates and want to add a new vCenter server along with the VMware vSphere plug-in, use the manageClientCerts -create option on the master server to generate a new certificate for the client. You can then use the newly generated certificate when you add the NetBackup master server to the VMware vSphere plug-in.