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
Add/Edit NetBackup Primary Servers within the Data Collector policy
Add and edit Veritas NetBackup servers directly from the data collector policy screen. These functions are also available from the .
The table, shown in the policy, is populated using either of these methods. Servers added from the policy are also displayed under . The table only displa ys available servers. These servers are not assigned to other policies within the domain.
Note:
Data Collector policies can be in place for multiple servers, but a server cannot be assigned multiple policies within the same domain. If you try add a server that is already assigned to another Data Collector policy, you will be prompted to remove it from its current policy and reassign it.
Click .
Select a Primary Server and click .
The window is displayed.
Enter or update values. Required fields are denoted by *.
Host Name: Name displayed in the portal. This is a required field.
Internal Host Name: Must match the host name of the Primary Server. If a Primary Server belongs to a cluster, enter the NetBackup Cluster Name for the Internal Name.
This is a required field.
IP Address: IP address of the host/backup server. This is a required field.
Make, Host Model, Host Location, Host Info Operating System, and OS Version, are optional.
Backup Type: Select Veritas NetBackup Primary. The field is displayed when the server is designated as a Primary Server. The Time Zone setting is only available for a host that is configured as a NetBackup Primary.
API Key: Enter the API key obtained from the Cohesity NetBackup Web UI to successfully execute the REST APIs. This API key must be specified in cases where password-based authentication is not allowed on the Cohesity NetBackup Primary Servers. For policies with Collection Method as NetBackup Software on a Data Collector Server, self-configured JWT tokens using certificates on the NetBackup Primary are used to execute the REST APIs. In this case, API Key is optional and will be used only when Data Collector is unable to get JWT token. Refer NetBackup Security and Encryption Guide for setting up certificates in NetBackup. See the Manage API keys section from the NetBackup Web UI Security Administrator's Guide for steps to get the API key.
See Prerequisites for collection from Cohesity NetBackup deployed on Kubernetes clusters.
Time Zones: Select a Time Zone to associate with the NetBackup Primary. Whenever the Time Zone is modified, the system marks the Data Collector as dirty so that the updates will be pushed to the Data Collector server. If the time zone is not explicitly configured for a NetBackup Primary, NetBackup IT Analytics defaults to the time zone of the Data Collector server. Note that in NetBackup IT Analytics reports, the date and time displayed for a backup transaction represents the date and time when the event actually happened.
Host Group Membership: Click to select a host group membership. Host group membership is mandatory when creating a backup server. A server can belong to multiple groups.