NetBackup IT Analytics Data Collector Installation Guide for the Cloud

Last Published:
Product(s): NetBackup IT Analytics (11.0)
  1. Pre-Installation Setup for Amazon Web Services (AWS)
    1.  
      Pre-Installation setup for Amazon Web services (AWS)
    2.  
      Prerequisites for adding Data Collectors (Amazon Web services)
    3.  
      Prerequisite Amazon Web services (AWS) configurations
    4.  
      Configure an S3 bucket to receive billing reports
    5.  
      Select cost allocation tags
    6. Create an AWS IAM user
      1.  
        Example of a custom AWS policy for NetBackup IT Analytics AWS collection
    7. Link AWS accounts for Collection of consolidated billing data
      1.  
        Create a role for NetBackup IT Analytics Data Collection
      2.  
        Add the role to the IAM user
    8.  
      Installation overview (Amazon Web Services - AWS)
    9.  
      Add an Amazon Web Services (AWS) policy
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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.  
      Install Data Collector in containerized environment
  7. 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
  8. Uninstalling the Data Collector
    1.  
      Uninstall the Data Collector on Linux
    2.  
      Uninstall the Data Collector on Windows
  9. Manually Starting the Data Collector
    1.  
      Introduction
  10. Appendix A. Firewall Configuration: Default Ports
    1.  
      Firewall configuration: Default ports

Select cost allocation tags

The Amazon Web Service (AWS) Data Collector supports the Cost and Usage Reports (CUR) only.

  1. Once the S3 bucket for Billing Report is created, configure the report name and the report prefix.

    CUR uses the following Amazon S3 organization and naming conventions.

    • Report-prefix: The prefix you assign to the report.

    • Report-name: The name you assign to the report.

    • yyyymmdd-yyyymmdd: The range of dates that the report covers. Reports are finalized at the end of the date range.

    • assemblyId: An ID that AWS creates each time when the report is updated.

    • file-number: If the update includes a large file, AWS might split it into multiple files. The file-number tracks the different files in an update.

    • CSV: The file format of the report.

    • ZIP / GZ: The type of compression applied to the report files.

  2. Select Cost Allocation Tags that have been assigned to your AWS resources so that they appear in the billing report and also so that they will be collected by the Data Collector. Tags are user-defined and enable groupings and totals for billing and reporting.

    User-defined tags are used for collection of EC2 and S3 resources. These tags are required for cost allocation reporting of the total cost of EC2 instances and S3 buckets.

    Note:

    Amazon Web Services generates a report once or more daily, with additions made daily over the month. Therefore, it may take up to 24 hours until a billing records file appears in the S3 bucket that is being collected by the NetBackup IT Analytics Data Collector.

  3. Create an AWS IAM user.

    See Create an AWS IAM user.