APTARE IT Analytics Certified Configurations Guide

Last Published:
Product(s): APTARE IT Analytics (10.5)
  1. Portal and database servers
    1.  
      Portal supported operating systems
    2.  
      Recommended portal configurations
    3.  
      Oracle Database and Memory Requirements
    4. Supported browsers and display resolution
      1.  
        Linux portal server: Exported and emailed reports
    5.  
      Supported third-party and open source products
  2. Data Collector server configurations
    1.  
      Data Collector supported operating systems
    2. Data Collector server memory and CPU guidelines
      1.  
        Customize the Linux file handle setting for large collections
      2.  
        Factors impacting Data Collector performance and memory requirements
    3.  
      Data Collector prerequisites
    4.  
      Firewall configuration: Default ports
  3. Capacity Manager configurations
    1.  
      Supported storage arrays and access requirements
    2.  
      IBM Arrays: Modify profile
    3.  
      Creating a NetApp user with API privileges
    4.  
      Creating a NetApp cluster-mode user with API privileges
    5. Array/LUN performance Data Collection
      1.  
        Port performance metrics
    6.  
      EMC Isilon metrics
    7.  
      NetApp cluster-mode metrics
    8.  
      EMC Symmetrix enhanced performance metrics
    9.  
      Host resources prerequisites and configurations
    10. Host access privileges, sudo commands, ports, and WMI proxy requirements
      1.  
        Access requirements by OS
    11.  
      WMI proxy requirements for Windows host Data Collection
    12.  
      Host resources supported configurations
    13.  
      Supported host bus adapters (HBAs)
  4. Cloud configurations
    1.  
      Supported systems and access requirements
  5. Virtualization Manager configurations
    1.  
      Supported versions
    2. Virtualization Manager Data Collector requirements for VMware
      1.  
        Creating a VMware Read-Only user
    3.  
      Virtualization Manager Data Collector requirements for Microsoft Hyper-V
  6. File Analytics configurations
    1. Data Collector probes by storage type
      1.  
        CIFS shares
      2.  
        Host inventory probe
  7. Fabric Manager configurations
    1. Switch vendors
      1.  
        Download Cisco Data Center Network Manager
  8. Backup Manager configurations
    1.  
      Backup solutions and versions
    2.  
      Centralized NetBackup Data Collection requirements
    3. Veritas NetBackup 8.1 (and later) requirements for centralized collection
      1.  
        Required Software
  9. Internal TCP port requirements
    1.  
      Internal TCP port requirements
    2.  
      Internal portal server ports
    3.  
      Internal data collector ports

Centralized NetBackup Data Collection requirements

  • Minimum Requirements: 64-bit OS, 2 CPUs or vCPUs and 32 GiB RAM.

  • If there is a firewall between the NetBackup Master Servers and the Data Collector Server, ensure that bi-directional port communication is open on ports 1556 and 13724.

  • For a NetBackup Centralized Data Collector (Linux or Windows OS), the Data Collector needs access to the Admin commands (CLI). This typically requires the NetBackup Master Server binaries to be installed on the Data Collector server. The CLI is available only with the Master Server binaries. Note that the installation of these binaries may require you to acquire a NetBackup Master Server license from Veritas.

  • See Veritas NetBackup 8.1 (and later) requirements for centralized collection.

  • The NetBackup software version on the Data Collector must match the major and minor version of the NetBackup software that is installed on the Master or Media Server that is being probed. When the Data Collector starts, it checks versions and halts collection for the Master Server where the mismatch is found. Refer to the Veritas documentation for more information about major and minor version requirements.

  • For SLP collection, a WMI Proxy Server is required. 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.

See Required Software.

Note:

If all NetBackup Masters configured in the collection policy are using the Linux operating system, then a WMI Proxy is not required.