NetBackup IT Analytics Release Notes

Last Published:
Product(s): NetBackup IT Analytics (11.1)
  1. Introduction
    1.  
      About NetBackup IT Analytics 11.1
  2. Patch release for version 11.1
    1. Patch releases: NetBackup IT Analytics
      1.  
        11.1.12 patch release notes
      2.  
        11.1.11 patch release notes
      3.  
        11.1.10 patch release notes
      4.  
        11.1.09 patch release notes
      5.  
        11.1.08 patch release notes
      6.  
        11.1.07 patch release notes
      7.  
        11.1.06 patch release notes
      8.  
        11.1.05 patch release notes
      9.  
        11.1.04 patch release notes
      10.  
        11.1.03 patch release notes
      11.  
        11.1.02 patch release notes
      12.  
        11.1.01 patch release notes
  3. What's new: Version 11.1 highlights
    1.  
      Supported product versions
    2.  
      Authorization attributes for user access control
    3.  
      Changes in Veritas terminology
    4.  
      Display custom notice on the portal login page
    5.  
      Probe introduced to collect security details from NetBackup environment
    6.  
      Configure password policy for portal domain users
    7.  
      Standalone reports to diagnose database performance issues
    8.  
      Exporter data to persist in the generic reports
    9.  
      Veritas Flex Appliance policy
    10.  
      Ransomware Scorecard
    11.  
      Deploy Data Collector Docker images into native Kubernetes cluster
    12.  
      Manage host aliases from NetBackup IT Analytics Portal
    13.  
      Microsoft Azure policy enhancement
    14.  
      Azure cost reports and dashboard
    15.  
      EMC Avamar Inclusion and Exclusion list enhancements - (Patch 2)
    16.  
      Enhancements in EMC Avamar data collection - (Patch 2)
    17.  
      Ransomware scorecard enhancement for RTO COMPLIANCE (Patch 1)
    18.  
      Ransomware scorecard enhancement for Pool Space (Patch 1)
    19.  
      Ransomware minimum version for NetBackup Primary parameter (Patch 4)
    20.  
      IT Analytics ServiceNow App certified on Tokyo and Utah releases
    21.  
      Hitachi Vantara DP Pool Summary (Patch 11.1.09)
    22.  
      Hitachi Vantara Efficiency Summary report (Patch 11.1.09)
    23.  
      Enhancements in Hitachi Vantara reports (Patch 11.1.10 and above)
  4. Supported Systems
    1.  
      Data Collector supported operating systems
    2. Supported browsers and display resolution
      1.  
        Linux portal server: Exported and emailed reports
  5. Installations and Upgrades
    1.  
      Portal installation memory requirements
    2.  
      Performance profiles and transmitted data
  6. Fixed issues
    1.  
      Overview
    2.  
      Fixed issues
  7. Known issues, optimizations, and End-of-Life (EOL)
    1.  
      Known issues
    2.  
      Optimization: Customize the Linux file handle setting for large collections
    3.  
      End-of-Life (EOL)

Optimization: Customize the Linux file handle setting for large collections

Certain environments may require optimizations to improve performance or to accommodate a large number of data collection policies.

In Linux, a portion of memory is designated for file handles, which is the mechanism used to determine the number of files that can be open at one time. The default value is 1024. For large collection policy environments, this number may need to be increased to 8192 so that the collector does not exceed the open file handle limit. A large environment is characterized as any collector that is collecting from 20 or more subsystems, such as 20+ TSM instances or 20+ unique arrays.

To change the number of file handles, take the following steps.

  1. On the Linux Data Collector server, edit /etc/security/limits.conf and at the end of the file, add these lines.

    root soft nofile 8192
    root hard nofile 8192
  2. Log out and log back in as root to execute the following commands to validate all values have been set to 8192.

    ulimit -n
    ulimit -Hn
    ulimit -Sn
    
  3. Restart the Data Collector.