Veritas™ Usage Insights for NetBackup Getting Started Guide

Last Published:
Product(s): NetBackup (10.3, 10.2, 10.1.1, 10.1, 10.0, 9.1, 9.0, 8.3)

Proxy support in Usage Insights

Usage Insights supports both authenticated and unauthenticated proxy servers when connecting to . Usage Insights supports both http and https protocols. These protocols are used by to relay Usage Insights data to Veritas.

Unauthenticated proxy support with http was first introduced in 8.3. With 9.1, authenticated proxy support and unauthenticated proxy support with https is also added.

The following proxy configurations are supported:

Table: version and proxy server configurations

version

Proxy server configuration

8.3 to 9.0

Unauthenticated proxy servers (no proxy user name or password) using HTTP.

Use the CALLHOME_PROXY_SERVER option that is set using the bpsetconfig command.

Upgrade to 9.1

  • Unauthenticated proxy servers (no proxy user name or password) using HTTPS.

  • Unauthenticated proxy servers (no proxy user name or password) using HTTP.

  • Authenticated proxy server that requires a proxy user name and a password using HTTP.

  • Authenticated proxy server that requires a proxy user name and a password using HTTPS.

Use the nbcallhomeproxyconfig command and the CALLHOME_PROXY_NAME option or manually configure the proxy using the Web UI after you upgrade to 9.1.

Fresh install of 9.1

  • Unauthenticated proxy servers (no proxy user name or password) using HTTPS.

  • Unauthenticated proxy servers (no proxy user name or password) using HTTP.

  • Authenticated proxy server that requires a proxy user name and a password using HTTP.

  • Authenticated proxy server that requires a proxy user name and a password using HTTPS.

Use the nbcallhomeproxyconfig command and the CALLHOME_PROXY_NAME option or manually configure the proxy using the Web UI after you install 9.1.

If you have set both CALLHOME_PROXY_SERVER and CALLHOME_PROXY_NAME, nbtelemetry uses CALLHOME_PROXY_NAME. CALLHOME_PROXY_SERVER is used only if CALLHOME_PROXY_NAME does not exist.