NetBackup IT Analytics Data Collector Installation and Configuration Guide for Cohesity 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
- Prerequisites for collection from Cohesity NetBackup deployed on Kubernetes clusters
- 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
- Configure Data Collector manually for Cohesity 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
Recover inadvertently deleted aptare.ks file
When aptare.ks gets deleted, there are no ways to encrypt/decrypt the keys stored in aptare_message_relay_keystore.properties. This procedure provides the steps to recover an inadvertently deleted keystore (aptare.ks) file.
To recover a keystore file:
- Login to the data collector system and navigate to its installation path:
/Aptare/mbs/conf. - Identify these files inside
/Aptare/mbs/conf:aptare_message_relay_certificate.pemaptare_message_relay_keystore.ksaptare_message_relay_keystore.properties
- Stop the Aptare Agent service on the data collector system.
On a Windows system, you can stop the service from the Services Console, whereas you can use ./aptareagent stop command on Unix.
- Delete these files from
/Aptare/mbs/conf.aptare_message_relay_certificate.pemaptare_message_relay_keystore.ksaptare_message_relay_keystore.properties
- Login to the NetBackup IT Analytics Portal to generate a new keystore file.
Since the certificate was changed, the portal will display a notification which states:
Data Collector SSL certificate has not been downloaded for collector(s): <data_collector_name>.
- Go to Admin > Data Collection > Collector Administration and click the collector name to view its policies.
- Double-click the collector to invoke the Edit Collector window.
- Copy the Passcode value and save it for later use.
- Click Generate Key and download the key file.
- Copy the key file to
/Aptare/mbs/conffolder on the data collector system. Ensure the file name is same as that of the data collector on the portal. - On the data collector system, open the collector.properties file from
/Aptare/mbs/confand replace the COLLECTOR_PASSWORD value with the Passcode value copied from the Edit Collector window. - Save the
collector.propertiesfile and start the Aptare Agent service.After the service starts:
A new
aptare.ksis generated inside/Aptare/mbs/confwhich consumes the new key file.. The
aptare_message_relay_certificate.pem,aptare_message_relay_keystore.ks, andaptare_message_relay_keystore.propertiesfiles are generated later shortly.Since the certificate was changed, the portal will display a notification which states:
Data Collector SSL certificate has not been downloaded for collector(s): <data_collector_name>.
- On the NetBackup IT Analytics Portal, go to Admin > Data Collection > Collector Administration and click the collector name to view its policies.
- Double-click the policy name for which SSL certificate needs to be downloaded. The policy configuration window is displayed.
- Click Download SSL Certificate. The certificate is downloaded to your system.
- Copy the certificate to the data sender trust store.