NetBackup IT Analytics Data Collector Installation and Configuration Guide for Veritas NetBackup
- Introduction
- Configure a NetBackup IT Analytics Distributed Data Collector on a NetBackup Primary Server
- Configure Data Collector on non-clustered NetBackup 10.4 and later primary server
- Configure Data Collector on non-clustered NetBackup 10.1.1, 10.2, 10.2.01, 10.3 or 10.3.0.1 primary server
- Configure a Veritas NetBackup Data Collector Policy
- Configuring file analytics in NetBackup Data Collector policy
- Installing the Data Collector software
- Configure SSL
- Centralized Data Collector for NetBackup - Prerequisites, Installation, and Configuration
- Step-1: Choose operating system and complete prerequisites
- Step-5: SSH/WMI
- Upgrading Data Collector Locally
- Clustering Data Collectors with VCS and Veritas NetBackup (RHEL)
- Clustering Data Collectors with VCS and Veritas NetBackup (Windows)
- Install and configure NetBackup IT Analytics Data Collector on MSCS environment
- Data Collector Policy Migration
- Pre-Installation setup for Veritas NetBackup appliance
- Pre-installation setup for Veritas Flex Appliance
- Data Collector Troubleshooting
- Host resources: Check host connectivity using standard SSH
- Host resources: Generating host resource configuration files
- Configuring parameters for SSH
- Appendix A. Configure Appliances
- Appendix B. Load historic events
- Load Veritas NetBackup events
- Appendix C. Firewall configuration: Default ports
- Appendix D. CRON Expressions for Policy and Report Schedules
- Appendix E. Maintenance Scenarios for Message Relay Server Certificate Generation
Linux Data Collector Prerequisites: Changing the Linux Temporary Directory for Collection
NetBackup IT Analytics uses temporary files on the target server for command output. The location of the temporary files is controlled by the TMPDIR environment variable, defaulting to /tmp.
NetBackup IT Analytics executes commands on the target NetBackup server using a non-interactive Bourne login shell (/bin/sh -l). On most systems this means that the /etc/profile
(when a login type of connection like ssh or scp is used) and ${HOME}/.bashrc
(when non-interactive connection like shell exec is used) files will be sourced and can be used to set the TMPDIR environment variable.
Log into the collection account on the target server.
Modify ${HOME}/.bashrc, set and export TMPDIR:
TMPDIR=/path/to/tmp export TMPDIR
For the NetBackup appliance: all CLI users share the
/home/nbusers
directory. To only change theTMPDIR
directory for the collection user, you must first check the logged-in user. For example:if [ "${USER}" = "itanalytics" ] ; then TMPDIR=/path/to/tmp export TMPDIR fi
To test, run the following command and verify that it returns the configured TMPDIR:
$ ssh <username>@127.0.0.1 '/bin/sh -l -c "echo \${TMPDIR}"' /path/to/tmp
Note:
There may be additional output before the TMPDIR path, for example the NBU appliance displays a banner.
The TMPDIR can be set either for all or a select set of target servers in a collector using the advanced parameter: NBU_SSH_TMPDIR. This value will be overridden if TMPDIR is set in the profile on the target server.
NBU_SSH_TMPDIR=/path/to/tm