NetBackup IT Analytics Installation and Upgrade Guide for Linux

Last Published:
Product(s): NetBackup IT Analytics (11.1)
  1. Install the NetBackup IT Analytics Portal on a Linux server
    1.  
      Introduction
    2.  
      Multi-language support and locale considerations (Linux)
    3.  
      OVA-based deployment on VMware ESXi
    4. Installer-based deployment
      1.  
        Task 1: Portal and database deployment strategies (Linux)
      2.  
        Task 2: Pre-installation configuration (Linux)
      3.  
        Task 3: Install Oracle database application binaries (Linux)
      4.  
        Task 4: Install the Portal application binaries (Linux)
      5.  
        Task 5: Installing the database schema (Linux)
      6.  
        Task 6: Start the Portal services (Linux)
      7.  
        Task 7: Request the license key file (Linux)
      8.  
        Task 8: Log into the Portal
      9.  
        Task 9: Install the license key file (Linux)
      10.  
        Task 10: Performing a cold backup of the database (Linux)
      11.  
        Recommended database backup process
    5.  
      Supported third-party and open source products
    6.  
      Uninstall the NetBackup IT Analytics Portal
  2. Upgrade NetBackup IT Analytics Portal on Linux
    1.  
      Overview
    2.  
      Upgrade path
    3.  
      Before upgrading
    4. Upgrade NetBackup IT Analytics Portal
      1.  
        Upgrade a shared services environment
      2.  
        Run the upgrade utility installer (Linux)
      3.  
        Known issues
      4.  
        Run the upgrade utility
      5.  
        After the upgrade
      6.  
        Upgrade methods to incorporate enterprise objects
      7. Attribute merging during the Portal upgrade
        1.  
          Attribute Management During the Portal Upgrade
        2.  
          Example of a Merge of Attribute Values
        3.  
          Steps to Rename Duplicate Attributes
        4.  
          Best Practice for Attributes in Multi-Tenancy Environments
    5. Data Collector upgrades
      1.  
        Mandatory prerequisites
    6.  
      Troubleshoot - Manual Data Collector upgrades
    7.  
      Collector updates from the NetBackup IT Analytics Portal
  3. Oracle patches for the database server
    1.  
      Apply Oracle-recommended patches
    2. Apply Oracle 19c April 2023 patch application on Linux
      1.  
        Pre-Install setup
      2.  
        OPatch installation steps
      3.  
        Installing the patches
      4.  
        Validate the database and OJVM patch
      5.  
        Validate the JDK version update
  4. Upgrade and Migrate to a new server
    1. Upgrade and migrate to a new server
      1.  
        Install the latest release of NetBackup IT Analytics on the new server
      2.  
        Perform an export of the database on the existing server
      3.  
        Stop Portal and agent services on the new server
      4.  
        Drop and re-create the existing portal user on the new server
      5.  
        Import the database onto the new server
      6.  
        Start Portal and agent services on the new server
      7.  
        Download, install, and execute to upgrade the database schema
    2.  
      Testing
    3.  
      Update Data Collector binaries (if necessary)
  5. Appendix A. X Virtual Frame Buffer
    1.  
      Configure X Virtual Frame Buffer (Xvfb)

Task 2: Pre-installation configuration (Linux)

  1. Choose a Portal Server.

    For performance reasons, avoid installing the NetBackup IT Analytics Portal software on the same server as the NetBackup IT Analytics Data Collectors. Precisely, avoid installing Data Collectors in /opt/aptare.

    If for some reason, you require both to be on the same server, ensure that both the Portal and Data Collector software do not reside in the same directory on the server. Portal software installation tasks require root privileges.

  2. For new Portal installations, the minimum server memory requirement is 32 GB. Oracle database requires a minimum of 24 GB of memory. Portal installations will fail if sufficient memory resources are not available on the Portal server.

  3. The Portal Installation software checks the following resources:

    • Total physical memory (physical + virtual) must be greater than 24 GB, otherwise Oracle will fail to start. Add more physical memory to the Portal server.

    • Total temporary file system (tmpfs) memory must be 24 GB or greater, otherwise Oracle will fail to start. Increase the size of tmpfs, typically in /etc/fstab.

    • Shared memory (kernel.shmmax parameter) must be 12 GB or greater, otherwise Oracle will fail to start. Increase the value of the shmmax parameter, typically in /etc/sysctl.conf. After increasing the value for the shmmax parameter, execute: sysctl -p.

  4. Verify the OS of the Portal Server. Check that the OS is one of the certified operating systems listed in the Certified Configurations Guide.

    Verify that sufficient disk space exists on the designated Portal Server. For the database file systems, the amount specified is the minimum to create the database. The database grows in size over the period of time. The growth of database dependents on various factors such as subsystems from which data is collected, type of systems collecting data from, retention periods for data(which is configurable), and so on.

    File

    System/

    Directory

    Minimum

    Disk Space

    Recommended Disk Space

    Maximum Disk Space for DB Growth

    Notes

    /opt

    20 GiB

    30 GiB

    30 GiB

    /tmp

    10 GiB

    10 GiB

    10 GiB

    Both /tmp and /var/tmp must be writable by the user aptare.

    /data01

    50 GiB

    100 GiB

    780 GiB

    Required for data and index tablespaces.

    /data02

    50 GiB

    100 GiB

    750 GiB

    Required for data and index tablespaces.

    /data03

    90 GiB

    250 GiB

    1800 GiB

    Required for data and index tablespaces.

    /data04

    65 GiB

    65 GiB

    65 GiB

    Temporary table space.

    /data05

    45 GiB

    45 GiB

    45 GiB

    Temporary table space (undo log).

    /data06

    5 GiB

    5 GiB

    5 GiB

    Temporary table space (redo log).

    Total

    335 GiB

    615 GiB

    3495 GiB

     
  5. Review third-party software details.

    See Supported third-party and open source products.

  6. If you plan to export or email reports as PDF files, to ensure proper rendering of these output formats, a graphics manager such as X Virtual Frame Buffer (Xvfb) is required. Contact your IT organization to configure this capability. See Configure X Virtual Frame Buffer (Xvfb).

  7. Verify the rpm fontconfig is installed. This is required for the Portal installer. Fontconfig is a library designed to provide system-wide font configuration, customization and application access. If the rpm fontconfig is not installed, exporting reports to XLS and PDF will fail.

  8. Verify that the necessary rpms exist on your system based on the OS.

    • For RHEL 8, use the following command:

      rpm -q perl-TermReadKey perl-Data-Dumper binutils glibc libaio elfutils-libelf perl-Getopt-Long binutils  gcc gcc-c++ glibc-devel ksh libaio-devel libgcc libstdc++ libXtst libXrender libstdc++-devel sysstat psmisc bc make libnsl.x86_64 --qf '%{name}.%{arch}\n'|sort

      The command returns:

    • bc.x86_64
      binutils.x86_64
      elfutils-libelf.x86_64
      gcc-c++.x86_64
      gcc.x86_64
      glibc-devel.x86_64
      glibc.x86_64
      ksh.x86_64
      libaio-devel.x86_64
      libaio.x86_64
      libgcc.x86_64
      libnsl.x86_64
      libstdc++-devel.x86_64
      libstdc++.x86_64
      libXtst.x86_64
      libXrender.x86_64
      make.x86_64
      perl-Data-Dumper.x86_64
      perl-Getopt-Long.noarch
      perl-TermReadKey.x86_64
      psmisc.x86_64
      sysstat.x86_64
      unzip
    • For RHEL 7 and CENTOS 7, use the following command:

      rpm -q perl-TermReadKey perl-Data-Dumper binutils glibc libaio elfutils-libelf perl-Getopt-Long compat-libcap1 compat-libstdc++-33 gcc gcc-c++ glibc-devel ksh libaio-devel libgcc libstdc++ libXtst libXrender libstdc++-devel sysstat psmisc bc make --qf '%{name}.%{arch}\n'|sort

      The command returns:

      bc.x86_64
      binutils.x86_64
      compat-libcap1.x86_64
      compat-libstdc++-33.x86_64
      elfutils-libelf.x86_64
      gcc-c++.x86_64
      gcc.x86_64
      glibc-devel.x86_64
      glibc.x86_64
      ksh.x86_64
      libaio-devel.x86_64
      libaio.x86_64
      libgcc.x86_64
      libstdc++-devel.x86_64
      libstdc++.x86_64
      libXtst.x86_64
      libXrender .x86_64
      make.x86_64
      perl-Data-Dumper.x86_64
      perl-Getopt-Long.noarch
      perl-TermReadKey.x86_64
      psmisc.x86_64
      sysstat.x86_64
      unzip
    • For SUSE Linux Enterprise, use the following command:

      The command returns:

      binutils.x86_64 
      glibc-devel.x86_64
      glibc.x86_64
      libaio-devel.x86_64
      libaio1.x86_64
      libcap-ng-utils.x86_64
      libcap-ng0.x86_64
      libcap-progs.x86_64
      libcap1.x86_64
      libcap2.x86_64
      libelf-devel.x86_64
      libgcc_s1.x86_64
      libjpeg-turbo.x86_64
      libjpeg62-turbo.x86_64
      libjpeg62.x86_64
      libpcap1.x86_64
      libpcre1.x86_64
      libpcre16-0.x86_64
      libpng16-16.x86_64
      libstdc++6.x86_64
      libtiff5.x86_64
      libXrender1.x86_64
      libXtst6.x86_64
      make.x86_64 
      mksh.x86_64
      perl-Term-ReadKey.x86_64
      pixz.x86_64
      rdma-core.x86_64
      smartmontools.x86_64
      sysstat.x86_64
      unzip
      xz.x86_64
  9. Verify that the bc command is available, as it is required by the database installer.

  10. Download the application binaries for both the Oracle Database Installer and the Portal Installer from www.veritas.com. Use the instructions provided in the confirmation of your purchase agreement.

  11. Troubleshooting User Account Creation: The Portal installation process will create user accounts for aptare and tomcat. If you are using non-local user management (such as LDAP or NIS) to manage the Linux user accounts, the useradd command may fail to execute successfully. Take the following steps to manually pre-create the required users:

    • Using your normal process for creating user accounts in LDAP, pre-create the user accounts aptare and tomcat with home directories under /home.

      User ID

      Primary Group

      Supplementary Groups

      aptare

      aptare

      dba

      tomcat

      tomcat

      aptare

    • Some environments, particularly virtualized ones using automount, will fail to create the home directories when the useradd command is used. In this situation, manually create the /home/aptare and /home/tomcat directories and chown them to aptare and tomcat respectively.

    • If you need additional clarification, contact the Veritas Support for details.

  12. Troubleshooting script issues: A known issue associated with Security Enhanced Linux (SELinux) may arise when executing scripts that require Java. This results in a permission denied error message. To resolve this issue, configure SELinux to allow the use of shared libraries with text relocation.

    The installer expects the SELinux configuration to be either disabled or permissive.

  13. Ensure ports 80/tcp, 8011, and 8017 are open in the firewall for proper functioning of the portal.

  14. Download following Oracle patches from www.veritas.com and keep them in a directory on the server where the Oracle Database will be installed.

    • p31281355_190000_Linux-x86-64.zip

    • p30565805_198000DBRU_Linux-x86-64.zip

    The path for this directory will requested by the Oracle database installer during the installation and upgrade process. The Oracle database installer will install these patches as part of installation or upgrade.

  15. Ensure that either ss or netstat command is available on the system.