APTARE IT Analytics Data Collector Installation Guide for Backup Manager
- Introduction
- Pre-Installation setup for Commvault Simpana
- Introduction
- Architecture overview (Commvault Simpana)
- Prerequisites for adding Data Collectors (Commvault Simpana)
- Upgrade troubleshooting: Microsoft SQL Server and Java 11
- Installation overview (Commvault Simpana)
- Open TCP/IP access to the Commvault database
- Set up a read-only user in the CommServe server
- Load historical data prior to initial data collection
- Add Commvault Simpana servers
- Add a Commvault Simpana Data Collector policy
- Pre-Installation setup for Cohesity DataProtect
- Pre-Installation setup for EMC Avamar
- Introduction
- Architecture overview (EMC Avamar)
- Prerequisites for adding Data Collectors (EMC Avamar)
- Installation overview (EMC Avamar)
- Add EMC Avamar servers
- Adding an EMC Avamar Data Collector policy
- Testing the collection
- Add/Configure an Avamar Server within the Data Collector policy window
- Import EMC Avamar server information
- Export EMC Avamar server information
- Pre-Installation setup for EMC Data Domain backup
- Architecture overview (EMC Data Domain Backup)
- Prerequisites for adding Data Collectors (EMC Data Domain Backup)
- Installation overview (EMC data domain Backup)
- Add EMC data domain servers
- Add an EMC data domain backup Data Collector policy
- Adding/Configuring an EMC data domain server within the Data Collector policy window
- Configure a data domain server for file-level compression collection
- Pre-Installation setup for EMC NetWorker
- Introduction
- Architecture overview (EMC NetWorker)
- Prerequisites for adding Data Collectors (EMC NetWorker)
- Installation overview (EMC NetWorker)
- Add EMC NetWorker servers
- Adding an EMC NetWorker Data Collector policy
- Adding/Editing a EMC NetWorker server within the Data Collector policy
- Configure a notification action in EMC NetWorker
- Pre-Installation setup for Dell EMC NetWorker backup & Recovery
- Pre-Installation setup for generic backup
- Introduction
- Generic backup data collection
- Prerequisites for adding Data Collectors (Generic Backup)
- Installation overview (generic backup)
- Add generic backup servers
- Add a generic backup Data Collector policy
- Adding/Editing a generic backup server within the Data Collector policy
- Manually load the CSV file (generic backup)
- CSV format specification
- Pre-Installation setup for HP Data Protector
- Introduction
- Architecture overview (HP Data Protector)
- Prerequisites for adding Data Collectors (HP Data Protector)
- Installation overview (HP Data Protector)
- Identify HP Data Protector collection requirements
- Cell Manager commands for data collection
- Preparing for centralized data collection on a remote Cell Manager
- Configure the Data Collector server in Cell Manager (HP Data Protector)
- Configure an HP Data Protector admin user
- Validate HP Data Protector setup
- Add HP Cell Manager servers to APTARE IT Analytics
- Add an HP Data Protector Data Collector policy
- Add/Edit a HP Data Protector server within the Data Collector policy
- Tune the configuration
- Pre-Installation setup for IBM Spectrum Protect (TSM)
- Introduction
- Architecture overview (IBM Spectrum Protect -TSM)
- Prerequisites for adding data collectors (IBM Spectrum Protect - TSM)
- Installation overview (IBM Spectrum Protect - TSM)
- Add IBM Spectrum Protect (TSM) servers
- Adding an IBM Spectrum Protect (TSM) Data Collector policy
- Add/Configure an IBM Spectrum Protect (TSM) server within the Data Collector policy
- Import IBM Spectrum Protect (TSM) information
- Export IBM Spectrum Protect (TSM) server information
- Pre-Installation setup for NAKIVO Backup & Replication
- Pre-Installation setup for Veritas Backup Exec
- Introduction
- Architecture overview (Veritas Backup Exec)
- Backup Exec terminology
- Prerequisites for adding data collectors (Veritas Backup Exec)
- Upgrade troubleshooting: Microsoft SQL Server and Java 10
- Installation overview (Veritas Backup Exec)
- Enable TCP/IP for the SQL server
- Configure a Windows user
- Add Veritas Backup Exec servers
- Importing Backup Exec Server information
- Add a Veritas Backup Exec Data Collector policy
- Pre-Installation setup for Veritas NetBackup
- Introduction
- General prerequisites for adding data collectors (Veritas NetBackup)
- Centralized or distributed deployment (Veritas NetBackup)
- Centralized NetBackup data collection (Recommended)
- Prerequisites to use SSH and WMI (Veritas NetBackup)
- Configure NetBackup Access Control (NBAC) for NetBackup Data Collection
- Configure NetBackup sudo access for NetBackup data collection
- Configure NetBackup Appliances for Data Collection
- Configure NetBackup Flex Appliances for Data Collection
- Veritas NetBackup SSH: Changing the Linux Temporary Directory for Collection
- Prerequisites for NetBackup collection over SSH (Kerberos option)
- Prerequisites for centralized NetBackup data collection (using NetBackup software)
- Veritas NetBackup 8.1 (or later) requirements for centralized collection
- Distributed NetBackup data collection
- Enable access to the Veritas NetBackup Master Server
- Before you install the Data Collector (Veritas NetBackup)
- Collecting from NetBackup clusters
- Clustered NetBackup upgrade procedure
- Add a Veritas NetBackup Data Collector policy
- Add/Edit NetBackup Master Servers within the Data Collector policy
- Configuring file analytics in NetBackup Data Collector policy
- Pre-Installation setup for Veritas SaaS backup
- Pre-Installation setup for Oracle Recovery Manager (RMAN)
- Pre-Installation setup for Rubrik Cloud Data Management
- Pre-Installation setup for Veeam Backup & Replication
- Introduction
- Prerequisites for adding data collectors (Veeam Backup & Replication)
- Verifying Data Collector servers can connect to Veeam servers
- Known issues and limitations (Veeam Backup & Replication)
- Installation overview (Veeam Backup & Replication)
- Add a Veeam Backup & Replication Data Collector policy
- Discovery policies for Veritas NetBackup
- Task overview: Configure and monitor discovery policies
- Discovery policies overview
- About Discovery types
- Activate a Discovery license
- Create and edit Discovery policies
- Exclude devices from Discovery policies
- Activate Discovery probes in the NetBackup Data Collector policy
- Monitor Discovery processes
- View client protection status
- Reset Discovery data
- Why enable SNMP?
- About SNMP probes
- Example--Installing Net-SNMP
- Troubleshoot Net-SNMP installations
- Installing the Data Collector software
- Introduction
- Installing the WMI Proxy service (Windows host resources only)
- Testing WMI connectivity
- Installing Data Collector software: From the internet
- Installing Data Collector software: No internet available from the Data Collector server
- Installing Data Collector software on Windows portal platform
- Installing Data Collector software on Linux portal platform
- Validate data collection
- Manually start the Data Collector
- Uninstall the Data Collector
- Appendix A. Load historic events
- Load historic events
- 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
- Appendix B. Firewall configuration: Default ports
Prerequisites for centralized NetBackup data collection (using NetBackup software)
Minimum Requirements: 64-bit OS, 2 CPUs or vCPUs and 32 GiB RAM.
If there is a firewall between the NetBackup Master Servers and the Data Collector Server, ensure that bi-directional port communication is open on ports 1556 and 13724. Also uses ports 1556 and 13724, WMI range of ports, Linux ssh 22.
For a centralized NetBackup Data Collector (Linux or Windows OS), the Data Collector needs access to the Admin commands (CLI). This requires the NetBackup Master Server binaries to be installed on the Data Collector server. The CLI is available only with the Master Server binaries. Note that the installation of these binaries may require you to acquire a NetBackup Master Server license from Veritas.
For Veritas NetBackup 8.1 and later, refer to the requirements.
See Veritas NetBackup 8.1 (or later) requirements for centralized collection.
The NetBackup software version on the Data Collector must match the major and minor version of the NetBackup software that is installed on the Master or Media Server that is being probed. When the Data Collector starts, it checks versions and halts collection for the Master Server where the mismatch is found. Refer to the Veritas documentation for more information about major and minor version requirements.
If you are currently running version 9.0 with centralized NetBackup data collection, and if the NetBackup software versions don't match, when you upgrade to APTARE Release Version 10 (or higher) data collection will cease for the Master Servers with the incompatible versions.
For SLP collection, a WMI Proxy Server is required.
See Required software.
WMI uses DCOM for networking. DCOM dynamically allocates port numbers for clients. DCOM's service runs on port 135 (a static port) and any client communicating with a host connects on this port. The DCOM service allocates the specific port for the WMI service. To set up a fixed port for WMI, see http://msdn.microsoft.com/en-us/library/bb219447%28VS.85%29.aspx.
Note:
If all NetBackup Master Servers configured in the collection policy are using the Linux operating system, then a WMI Proxy is not required.