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
- Overview
- Configure Data Collector on non-clustered NetBackup 10.4 and later primary server
- Configuration workflow for NetBackup 10.1.1, 10.2, 10.2.01, 10.3 or 10.3.0.1 on a non-clustered NetBackup 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
- Configuration workflow for NetBackup versions lower than 10.1.1
- Configure Data Collector on NetBackup primary with version lower than 10.1.1
- Configure a Veritas NetBackup Data Collector Policy
- Veritas NetBackup Data Collector policy configuration prerequisites
- Create NetBackup Data Collector Role, Service Account, and API Key
- Add a Veritas NetBackup Data Collector policy
- Add/Edit NetBackup Primary Servers within the Data Collector policy
- Configuring file analytics in NetBackup Data Collector policy
- Installing the Data Collector software
- Introduction
- Considerations to install Data Collector on non-English systems
- Install Data Collector Software on Windows
- Install Data Collector software on Linux
- Deploy Data Collector in native Kubernetes environment
- Configure Data Collector manually for Veritas NetBackup
- Install Data Collector binaries on Windows (without configuration)
- Install Data Collector binaries on Linux host (without configuration)
- Override default Java Heap memory (XMX) value for Data Collector utilities
- Configure SSL
- SSL/TLS certificate configuration
- SSL implementation overview
- Obtain an SSL certificate
- Update the web server configuration to enable SSL on the Portal server
- Enable / Disable SSL for a Data Collector
- Enable / Disable SSL for emailed reports
- Test and troubleshoot SSL configurations
- Keystore file locations on the Data Collector server
- Import a certificate into the Data Collector Java keystore
- Keystore on the portal server
- Add a virtual interface to a Linux server
- Add a virtual / secondary IP address on Windows
- Centralized Data Collector for NetBackup - Prerequisites, Installation, and Configuration
- Overview
- Step-1: Choose operating system and complete prerequisites
- Step-2: HTTPS requirement
- Step-3: Add Data Collector on NetBackup IT Analytics Portal
- Step-4: Create NetBackup Data Collector Role, Service Account, and API Key
- Step-5: SSH/WMI
- Step-6: Install the Data Collector
- Step-7: Configure Data Collector
- Step-8: Verify the Data Collector is online from the Portal
- Step-9: Confirm that the Data Collector is updated
- Step-10: Configure the data collection policy
- Step-11: Confirm that the NetBackup data collection policy is collecting data
- Upgrading Data Collector Locally
- Overview
- Verification of upgrade bundle available on Data Collector server
- Upgrade the Upgrade Manager component
- Upgrade the Data Collector component which is the aptare.jar file
- Upgrade the Upgrade Manager and Data Collector components together
- Upgrade logs and upgrade related database views
- Resolve file lock issue on Windows host during Data Collector upgrade
- 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
- Resolving Data Collectors connections issues - Linux specific
- Resolving Data Collectors connections issues - Windows specific
- Portal upgrade performance issues
- Configuring web proxy updates
- Host resources troubleshooting
- Host resources: Check the status of the WMI proxy server
- Host resources: Post-Installation verification
- Host resources: Check host connectivity using standard SSH
- Host resources: Check host connectivity
- Host resources: Check host connectivity using Host Resource Configuration file
- Host resources: Generating host resource configuration files
- Host resources: Check the execution of a command on a remote server
- Host resources Data Collection
- Host resources: Collection in stand-alone mode
- Configuring parameters for SSH
- Identifying Windows file system access errors (File Analytics)
- Collect from remote shares (File Analytics)
- Adding a certificate to the Java keystore
- Override default Java Heap memory (XMX) value for Data Collector utilities
- Appendix A. Configure Appliances
- Appendix B. Load historic events
- Introduction
- Load Commvault Simpana events
- Load EMC Avamar events
- Load EMC NetWorker events
- Load HP Data Protector events
- Load IBM Spectrum Protect (TSM) events
- Load Oracle Recovery Manager (RMAN) events
- Load Veeam Backup & Replication events
- Load Veritas NetBackup events
- Load Veritas Backup Exec events
- Corrections in duplication of clients
- Cohesity
- Dell EMC NetWorker Backup & Recovery
- 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
Load Commvault Simpana events
Commvault Simpana Historic Collection uses a JDBC connection to collect jobs data from the Commvault Simpana database for a given look back hours.
Configure COMMVAULT_OLDEST_JOB_HOURS parameter for historic data collection.
Note:
The allowed maximum number of hours to look back for historic data collection is 168 hours. Historic collection is normally used on first time collection. It retrieves the details of the backup jobs, restore jobs, and job failures from the database using the SQL queries.
Windows:
C:\Program Files\Aptare\mbs\bin\commvault\cvsimpanadetails.bat
Linux:
<APTARE HOME>/mbs/bin/commvault/cvsimpanadetails.sh
To capture data from a specific period, use the following utility:
cvsimpanadetails.{sh|bat} <output_dir> <cvdb_username> <cvdb_password>
<cvdb_hostname>[:port] [max_hours [cv_username cv_password [cv_hostname]]]Where:
This utility will write data to a set of files in the output directory specified in
output_dir.The cvdb_username, cvdb_password and cvdb_hostname refer to the CommServ database system (this is usually the same as the CommServ server) from which you are collecting data.
[Optional]Port Number can be appended to the cvdb_hostname, separated by a colon.
Note:
If a port number is not specified, default 1433 port is assigned.
[Optional]Maximum number of hours from which to start the collection can be specified. This value is used to calculate the current time minus the number of hours that was entered.
If you do not enter a maximum number of hours, then all details retained by the Commvault Simpana database will be retrieved.
The last set of cv_username, cv_password and cv_hostname are required only if you are collecting Skipped File Details from a Windows-based CommServ Server.