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

Prerequisites for adding data collectors (Microsoft Hyper-V)

Identify a server where the Data Collector software will be installed. Server requirements include:

  • 64-bit OS. See the Certified Configurations Guide for supported operating systems.

  • When the NetBackup IT Analytics system collects data from any vendor subsystem, the collection process expects name/value pairs to be in US English, and requires the installation to be done by an Administrator with a US English locale. The server's language version can be non-US English.

  • For performance reasons, do not install Data Collectors on the same server as the NetBackup IT Analytics Portal. However, if you must have both on the same server, verify that the Portal and Data Collector software do not reside in the same directory.

  • Install only one Data Collector on a server (or OS instance).

  • The collector must have WMI network access to the Hyper-V servers. User credentials must allow access to the root\cimv2, root\virtualization\v2 and root\MSCluster WMI namespaces.

  • The Data Collector Service that is initially installed uses the Local System as the Log in account. Sometimes this account does not have permissions to run remote WMI commands. You should instead change the Service configuration to use a Log in account that has Local Administrative privileges.

  • The collector uses a PowerShell script that uses WMI to communicate with the Hyper-V, and makes a number of read-only calls to gather the information. PowerShell script execution must be enabled on the system running this script. The version of PowerShell on the system must be 5.0 or above.

  • A full collection path to Hyper-V server attached SAN or NAS storage requires that Host Resource collection be run first against the Hyper-V servers.

  • WMI uses DCOM for networking. DCOM dynamically allocates port numbers for clients. DCOM's service runs on port 135 (a static port) and any client communicating with a host connects on this port. The DCOM service allocates the specific port for the WMI service.

To set up a fixed port for WMI, see http://msdn.microsoft.com/en-us/library/bb219447%28VS.85%29.aspx.