NetBackup IT Analytics Data Collector Installation Guide for the Cloud

Last Published:
Product(s): NetBackup IT Analytics (11.4)
  1. Pre-installation setup for Google Cloud Platform
    1.  
      Overview
    2.  
      Pre-installation setup for GCP
    3.  
      Prerequisites for adding Data Collectors (GCP)
    4.  
      Installation GCP
    5.  
      Adding policy
    6.  
      Testing the collection
    7.  
      Creating an IAM role
    8.  
      Billing Data Access Role
    9.  
      Cloud API
    10.  
      Project access
  2. Pre-Installation Setup for OpenStack Ceilometer
    1.  
      Pre-Installation setup for OpenStack Ceilometer
    2.  
      Prerequisites for adding Data Collectors (OpenStack Ceilometer)
    3.  
      Installation Overview (OpenStack Ceilometer)
    4.  
      Adding an OpenStack Ceilometer Data Collector policy
  3. Pre-Installation Setup for OpenStack Swift
    1.  
      Pre-Installation setup for OpenStack Swift
    2.  
      Prerequisites for adding Data Collectors (OpenStack Swift)
    3.  
      Installation overview (OpenStack Swift)
    4.  
      Adding an OpenStack Swift Data Collector policy
  4. Pre-Installation Setup for Microsoft Azure
    1.  
      Pre-Installation setup for Microsoft Azure
    2.  
      Setting up credentials for Microsoft Azure Data Collection
    3.  
      Install the Azure PowerShell client on a Windows computer
    4.  
      Find your tenant and subscription ID
    5.  
      Register a new application for the Data Collector
    6.  
      Create a principal and assign role to the application
    7.  
      Prerequisites for Adding Data Collectors (Microsoft Azure)
    8.  
      Installation overview (Microsoft Azure)
    9.  
      Add a Microsoft Azure Data Collector policy
  5. Installing the Data Collector Software
    1.  
      Introduction
    2.  
      Installing the WMI Proxy service (Windows host resources only)
    3.  
      Testing WMI connectivity
    4.  
      Install Data Collector Software on Windows
    5.  
      Install Data Collector software on Linux
    6.  
      Deploy Data Collector in native Kubernetes environment
    7.  
      Configure Data Collector manually for Veritas NetBackup
    8.  
      Install Data Collector binaries on Windows (without configuration)
    9.  
      Install Data Collector binaries on Linux host (without configuration)
  6. Validating Data Collection
    1.  
      Validation methods
    2.  
      Data Collectors: Vendor-Specific validation methods
    3. Working with on-demand Data Collection
      1.  
        View real-time logging during an on-demand collection
      2.  
        Generating debug level logs during an on-demand collection
    4.  
      Using the CLI check install utility
    5.  
      List Data Collector configurations
  7. Uninstalling the Data Collector
    1.  
      Uninstall the Data Collector on Linux
    2.  
      Uninstall the Data Collector on Windows
  8. Manually Starting the Data Collector
    1.  
      Introduction
  9. Appendix A. Firewall Configuration: Default Ports
    1.  
      Firewall configuration: Default ports

Adding an OpenStack Ceilometer Data Collector policy

  • Before adding the policy: A Data Collector must exist in the Portal, to which you will add Data Collector Policies.

    For specific prerequisites and supported configurations for a specific vendor, see the Certified Configurations Guide.

  • After adding the policy: For some policies, collections can be run on-demand using the Run button on the Collector Administration page action bar. The Run button is only displayed if the policy vendor is supported.

    On-demand collection allows you to select which probes and devices to run collection against. This action collects data the same as a scheduled run, plus logging information for troubleshooting purposes. For probe descriptions, refer to the policy.

To add the policy

  1. Select Admin > Data Collection > Collector Administration. Currently configured Portal Data Collectors are displayed.
  2. Search for a Collector if required.
  3. Select a Data Collector from the list.
  4. Click Add Policy, and then select the vendor-specific entry in the menu.
  5. Enter or select the parameters. Mandatory parameters are denoted by an asterisk (*):

    Field

    Description

    Collector Domain

    The domain of the collector to which the collector backup policy is being added. This is a read-only field. By default, the domain for a new policy will be the same as the domain for the collector. This field is set when you add a collector.

    Policy Domain

    The Policy Domain is the domain of the policy that is being configured for the Data Collector. The Policy Domain must be set to the same value as the Collector Domain. The domain identifies the top level of your host group hierarchy. All newly discovered hosts are added to the root host group associated with the Policy Domain.

    Typically, only one Policy Domain will be available in the drop-down list. If you are a Managed Services Provider, each of your customers will have a unique domain with its own host group hierarchy.

    To find your Domain name, click your login name and select My Profile from the menu. Your Domain name is displayed in your profile settings.

    Authentication Server Address*

    Enter the IP address of the server with Identity Service and port number in the format: <ip address>:<port_number>. The port number is NOT required if you are running on the default port 35357. However, if you are running on a port other than the default, you must specify the port number.

    Port

    Ceilometer API service port.

    User ID*

    Enter a user ID that has access to the tenants/projects. This user must have an Admin role, which has access to all projects.

    Password*

    Enter the password associated with the User ID.

    Compute Performance

    Collect metrics based on the length of time since the last collection cycle to a maximum of one hour. One collection per hour is the recommended time period.

    Notes

    Enter or edit notes for your data collector policy. The maximum number of characters is 1024. Policy notes are retained along with the policy information for the specific vendor and displayed on the Collector Administration page as a column making them searchable as well.

    Test Connection

    Test Connection initiates a Data Collector process that attempts to connect to the subsystem using the IP addresses and credentials supplied in the policy. This validation process returns either a success message or a list of specific connection errors. Test Connection requires that Agent Services are running.

    Several factors affect the response time of the validation request, causing some requests to take longer than others. For example, there could be a delay when connecting to the subsystem. Likewise, there could be a delay when getting the response, due to other processing threads running on the Data Collector.

    You can also test the collection of data using the Run functionality available in Admin>Data Collection>Collector Administration. This On-Demand data collection run initiates a high-level check of the installation at the individual policy level, including a check for the domain, host group, URL, Data Collector policy and database connectivity. You can also select individual probes and servers to test the collection run.