NetBackup IT Analytics Installation and Upgrade Guide for Linux

Last Published:
Product(s): NetBackup IT Analytics (11.4)
  1. Installation overview
    1.  
      Introduction
    2.  
      NetBackup IT Analytics components
    3.  
      Standard or Shared Services licensing edition
    4.  
      Install options
    5.  
      Multi-language support and locale considerations (Linux)
    6.  
      Supported third-party and open source products
  2. Install NetBackup IT Analytics on a Linux server
    1.  
      Step-1: Get the NetBackup IT Analytics license key file
    2.  
      Step-2: Portal and database deployment strategies
    3.  
      Step-3: Portal and database prerequisites
    4. Step-4: Install Oracle database application binaries (Linux)
      1.  
        Create database and users in existing Oracle farm in a Split Architecture deployment
    5.  
      Step-5: Install the Portal application binaries (Linux)
    6.  
      Step-6: Start the Portal services (Linux)
    7.  
      Step-7: Log into the Portal
    8.  
      Step-8: Install a license
    9. Verify the current license configuration
      1.  
        Run the License Summary report
      2.  
        About NetBackup IT Analytics version and license
      3.  
        View License Details
    10. Next steps
      1.  
        Performing a cold backup of the database
      2.  
        Recommended database backup process
  3. 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.  
      Troubleshoot Data Collector upgrade manager upgrade failure and collector bundle download failure on Linux
    8.  
      Collector updates from the NetBackup IT Analytics Portal
  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)
  6. Appendix B. Oracle patches for the database server
    1. Apply Oracle 19c October 2024 patch application
      1.  
        Pre-Install setup
      2.  
        OPatch installation steps
      3.  
        Installing the Oracle patches
      4.  
        Validate the database and OJVM patches
      5.  
        Validating JDK version update

Step-3: Portal and database prerequisites

  1. Choose a Portal Server. Install the NetBackup IT Analytics Portal software on its own, dedicated server. For performance reasons, the NetBackup IT Analytics Portal software must not be installed on the same server as the Data Collector. Root privileges are required for the Portal software installation tasks.

  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 Oracle server has the following memory requirements:

    • 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.

    • Swap space of minimum 16 GB must be created.

  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.

    NetBackup IT Analytics supports installation of binaries and database files at custom locations on the file system. By default, the binaries are installed under /opt and the database files are created under /data01 through /data06 folders. If you choose to install at the default path, the file system space requirements must be as below.

    File

    System/

    Directory

    Minimum

    Disk Space

    Recommended Disk Space

    Maximum Disk Space for DB Growth

    Notes

    /opt

    20 GiB

    50 GB

    50 GB

    		 

    /tmp

    2 GiB

    2 GiB

    10 GiB

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

    /data01

    50 GiB

    100 GiB

    750 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).

    If you choose to install at a custom path, the file and space requirements are as below:

    <install_path>

    (custom install path of the Portal)

    20 GiB

    30 GiB

    30 GiB

    		 

    /tmp

    2 GiB

    2 GiB

    10 GiB

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

    <install_path>

    (custom install path of the database)

    305 GiB

    565 GiB

    3445 GiB

    		 

    If you choose to install a custom path with Split Architecture, the file and space requirements are as below:

    /opt/aptare (install_path for oracle on Database server)

    10 GiB

    30 GiB

    30 GiB

    		 

    /opt (install_path for Portal on Portal server)

    10 GiB

    30 GiB

    30 GiB

    		 

    /tmp

    2 GiB

    2 GiB

    10 GiB

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

    /data01

    /data02

    /data03

    /data04

    /data05

    /data06

    300 GiB

    560 GiB

    3400 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 formats will fail.

  8. If the Portal system is having low entropy, it can affect the performance of cryptographic functions and such steps can take considerable amount of time to complete. You can identify the entropy level of the system from the content of the /proc/sys/kernel/random/entropy_avail file using command # cat /proc/sys/kernel/random/entropy_avail. If this value is not more than 400 consistently, install the rng-tools and start the services as described below on the Portal system.

    For RHEL or OEL:

    • Access the command prompt.

    • Install the rng-tools.

      yum install rng-tools

    • Start the services.

      systemctl start rngd

    • Enable the services.

      systemctl enable rngd

    For SUSE:

    • Access the command prompt.

    • Install the rng-tools.

      zypper install rng-tools

    • Start the services.

      systemctl start rng-tools

    • Enable the services.

      systemctl enable rng-tools

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

    • For RHEL 9, use the following command:

      rpm -q bc binutils compat-openssl11 elfutils-libelf fontconfig gcc glibc glibc-devel ksh libaio libasan liblsan libX11 libXau libXi libXrender libXtst libxcrypt-compat libgcc libibverbs libnsl librdmacm libstdc++ libxcb libvirt-libs make policycoreutils policycoreutils-python-utils smartmontools sysstat perl-TermReadKey perl-English-1.11-480.el9.noarch --qf '%{name}.%{arch}\n'|sort

      The command returns:

      bc.x86_64
binutils.x86_64
compat-openssl11.x86_64
elfutils-libelf.x86_64
fontconfig.x86_64
gcc.x86_64
glibc-devel.x86_64
glibc.x86_64
ksh.x86_64
libaio.x86_64
libasan.x86_64
libgcc.x86_64
libibverbs.x86_64
liblsan.x86_64
libnsl.x86_64
librdmacm.x86_64
libstdc++.x86_64
libvirt-libs.x86_64
libX11.x86_64
libXau.x86_64
libxcb.x86_64
libxcrypt-compat.x86_64
libXi.x86_64
libXrender.x86_64
libXtst.x86_64
make.x86_64
perl-English.noarch
perl-TermReadKey.x86_64
policycoreutils-python-utils.noarch
policycoreutils.x86_64. 
smartmontools.x86_64
sysstat.x86_64

      The following Oracle patches are required to install the Oracle 19c database on a RHEL9 host for both Standard Edition and Shared Edition licenses. Download these 4 patches from the Veritas Download Center if Oracle is provided by Veritas or from Oracle Support Center if you have your own Oracle license.

      • patch 35775632 (p35775632_190000_Linux-x86-64.zip)

      • patch 6880880 by selecting the 19.0.0.0.0 release (p6880880_190000_Linux-x86-64.zip)

      • 19.20 DBRU Patch 35320081 (p35320081_190000_Linux-x86-64.zip)

      • 19.20 DB MLR 35904951 (p35904951_1920000DBRU_Linux-x86-64.zip)

    • 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 12 Linux Enterprise, use the following command:

      rpm -q bc.x86_64 binutils.x86_64 glibc-devel.x86_64 glibc.x86_64 libaio-devel.x86_64 libaio1.x86_64 libcap-ng-us.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  --qf '%{name}.%{arch}\n'|sort

      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

    • For SUSE 15 Linux Enterprise, use the following command:

      rpm -q bc.x86_64 binutils.x86_64 compat-libpthread-nonshared.x86_64  glibc-devel.x86_64 glibc.x86_64 libaio-devel.x86_64 libaio1.x86_64 libcap-ng-us.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  --qf '%{name}.%{arch}\n'|sort

      The command returns:

      binutils.x86_64 
compat-libpthread-nonshared.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

  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 of 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

      apache

      		 

      apache

      		  

      You can customize these user group names or create them in advance according to your organization's user management policy. Copy the config.sh file inside the ISO mount path to the local system, edit it appropriately, and then pass the absolute path of config.sh to the installer script with -C option.

      Example:

      <Installer_script> -C <path of config.sh>

Itanalyticsinstaller.sh -C /tmp/config.sh

    • 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. Ensure that either ss or netstat command is available on the system.