NetBackup IT Analytics Data Collector Installation Guide for Virtualization Manager

Last Published:
Product(s): NetBackup IT Analytics (11.2)
  1. Pre-Installation setup for VMware
    1.  
      Pre-Installation setup for VMware
    2.  
      VMware Data Collection
    3. Prerequisites for adding data collectors (VMware)
      1.  
        Virtualization Manager: Collection of VMware Data
      2. Configure VMware Access
        1.  
          Pre-requisites for vSAN Data Collection
        2.  
          Creating a VMware Read-Only User with Required Permissions
    4.  
      Installation overview (VMware)
    5.  
      Add a VMware Data Collector policy
    6. Datastore scan collection
      1.  
        Reports impacted by Datastore Collection
  2. Pre-Installation setup for IBM VIO
    1.  
      Pre-Installation setup for IBM VIO
    2.  
      Prerequisites for adding data collectors (IBM VIO)
    3.  
      Installation overview (IBM VIO)
    4.  
      Adding servers for the IBM VIO Data Collector policy
    5.  
      VIO servers (IBM Virtual I/O Servers)
    6.  
      LPAR clients (IBM Logical Partitioning Clients) managed by VIO servers
    7.  
      HMC (IBM Hardware Management Console)
    8.  
      Add an IBM VIO Data Collector policy
  3. Pre-Installation setup for Microsoft Hyper-V
    1.  
      Pre-Installation setup for Microsoft Hyper-V
    2.  
      Prerequisites for adding data collectors (Microsoft Hyper-V)
    3.  
      Installation overview (Microsoft Hyper-V)
    4.  
      Add a Microsoft Hyper-V Data Collector policy
  4. Install the Data Collector software
    1.  
      Introduction
    2.  
      Installing the WMI Proxy service (Windows host resources only)
    3.  
      Testing WMI connectivity
    4.  
      Considerations to install Data Collector on non-English systems
    5.  
      Install Data Collector Software on Windows
    6.  
      Install Data Collector software on Linux
    7.  
      Deploy Data Collector in native Kubernetes environment
    8.  
      Configure Data Collector manually for Veritas NetBackup
    9.  
      Install Data Collector binaries on Windows (without configuration)
    10.  
      Install Data Collector binaries on Linux host (without configuration)
  5. 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
  6. Uninstall the Data Collector
    1.  
      Uninstall the Data Collector on Linux
    2.  
      Uninstall the Data Collector on Windows
  7. Manually start the Data Collector
    1.  
      Introduction
  8. Appendix A. Firewall configuration: Default ports
    1.  
      Firewall configuration: Default ports

LPAR clients (IBM Logical Partitioning Clients) managed by VIO servers

By configuring collection for IBM LPAR clients through the data collector policy, all newly discovered LPARs found using the collector policy will automatically have the host probes activated. The eliminates the requirement of manually enabling the probes using Host Discovery.

  1. On the IBM VIO data collector policy, click the checkbox Enable Host Collection. This activates the Configure Host Collection button.

  2. Click Configure Host Collection.

  3. Configure capacity probes for each of the LPAR Clients according to the following guidelines:

  • Capacity: enable.

  • HBA Probe:

    • If the disks are given to LPAR Clients using VSCSI, the HBA Probe should be disabled since the LPAR Clients are not connected directly to the SAN.

    • If the disks are given to LPAR Clients using NPIV, the HBA Probe should be enabled.

  • Volume Manager: enable.

  • Multi-pathing:

    • If the LPAR Clients have any third-party multi-pathing software such as EMC PowerPath or Hitachi HDLM Multipathing, the Multipath Probe should be enabled.

    • If the LPAR Clients are using native AIX multi-pathing, the Multi-path Probe should be disabled.