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
Create and edit Discovery policies
Discovery is a policy-based module that enables you to tune and configure parameters for the Discovery engine. You must create a Discovery policy for each Veritas NetBackup master server and for each Discovery type that you want to enable on them.
Discovery policies are executed on the master servers at intervals that you can set. Although the values that you specify for these "wake-up" intervals reside in a configuration file, the recommendation is that you update these intervals via the Portal, not the configuration file.
See Discovery policies overview .
To create Discovery policies
- Determine the master server that requires the policy that you are about to create.
- Select Admin > Reports > NetBackup Discovery to display the list of master servers in the Discovery Administration window.
- Select a Management Server and click Edit. You also can double-click the server.
Three Discovery processes can be scheduled via this Discovery Administration window:
New server discovery
Media server file systems
NetBackup server file systems
- Set the times that specify when the Discovery process will be executed.
The format for the time:
*
minutes
*
hours
*
day of month
*
month
*
day of week
The following tables list the allowed and default values.
Field
Allowed Values
minutes
0-59
hours
0-23
days of the month
1-31
month
1-12
days of week
1-7 (1 is Sunday)
Note:
A field may also be an asterisk (*), which means the full range - i.e. "first" to "last".
When configuring the start window, you need to consider the wake-up period of the Discovery processes. If you configure a window of "* 2-3 1 * *" (that is, between 2 and 3 am on the first day of each month) for the New Server Discovery process, the process might run twice if it wakes up at 2am, takes 15 minutes to execute, sleeps for 40 minutes, then wakes up again at 2:55am. Since the start window is still active at 2:55am, it will run again.
Discovery Type
Wake-up Time Default
Start Window Default Values
New Server Discovery
40 minutes
* 14-15 * * 1 (Every Monday, between 2 and 3pm)
Media Server Discovery
20 minutes
* * * * * (Anytime - i.e. runs every 20 minutes)
NetBackup Client File Systems
35 minutes
* 16-17 * * 1 (Every Monday, between 4 and 5pm)
1-31
month
1-12
days of week
1-7 (1 is Sunday)
- For each device that Discovery must probe:
In the Discovery Administration window, click Add to add a device or select device and click Edit.
In the IP address range field, enter either a single IP address or an IP address range.
An IP range is in the format nnn-nnn (For example: 172.16.100-110.1-255 covers 11*255 = 2805 IP addresses). Multiple ranges can be added and each range can be independently activated or deactivated via the active check box.
The Media Server Discovery Policy automatically generates the list of devices to probe - essentially all media servers associated with the management server. Similarly, the NetBackup Server File System Discovery Policy automatically generates the list of servers to probe by finding all servers contained in policies on that management server.
- Click OK to save your settings.