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
Add a virtual interface to a Linux server
The standard APTARE server configuration uses two virtual hosts on the server. One host, identified by the sub-domain
, handles Portal requests to deliver NetBackup IT Analytics administration and reporting functionality. The second host, identified by the sub-domain , handles data collection functionality between the data collection agent and the various devices that report to the agent. These virtual hosts are defined in the Apache configuration file; the sub-domain names are used to identify the each host.When using SSL, unique IP addresses must be assigned to each virtual host. Therefore, if SSL is to be enabled for both the Portal and Data Collection, two IP addresses are required. Two IP addresses can be assigned using two NICs or, on a Linux server, a virtual interface can be created to assign two IP addresses to a single NIC.
To verify the number of IP addresses assigned to a Linux server, use the following command:
ifconfig -a
Example result of the ifconfig -a command:
eth0 Link encap:Ethernet HWaddr 08:00:27:71:44:C4 inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:310 errors:0 dropped:0 overruns:0 frame:0 TX packets:372 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:63235 (61.7 KiB) TX bytes:28143 (27.4 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8762 errors:0 dropped:0 overruns:0 frame:0 TX packets:8762 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5422509 (5.1 MiB) TX bytes:5422509 (5.1 MiB)
You must have two Ethernet connections, identified by the eth0 label. To add a virtual interface on a Linux server, with a second IP address, to the existing Ethernet interface, use the following command:
ifconfig eth0:0 111.222.333.444
where
111.222.333.444 is the new IP address for the virtual interface.
You must add a file to the network scripts to recreate the virtual interface when the server is rebooted. If the IP address assigned to the eth0 interface is static, make a copy of the ifcfg-eth0 file in /etc/sysconfig/network-scripts and name it ifcfg-eth0:0.
Update the IP address in ifcfg-eth0:0 to be the new IP address assigned to the virtual interface.
If the IP address in the eth0 interface is dynamically assigned, as indicated by the line BOOTPROTO=dhcp in the ifcfg-eth0 file, create a file named ifcfg-eth0:0 with the following lines:
DEVICE=eth0:0 IPADDR=111.222.333.444
Finally, update your DNS server so that the new IP address is mapped to the data collection URL (for example, itanalyticsportal.<domainname>).