NetBackup IT Analytics Data Collector Installation Guide for Capacity Manager
- Overview
- Pre-Installation setup for Compute Resources
- Pre-Installation setup for Dell Compellent
- Pre-Installation setup for DELL EMC Elastic Cloud Storage (ECS)
- Pre-Installation setup for Dell EMC Unity
- Pre-Installation setup for EMC data domain storage
- Pre-Installation setup for EMC Isilon
- Pre-Installation setup EMC Symmetrix
- Pre-Installation setup for EMC VNX Celerra
- Pre-Installation setup for EMC VNX
- Pre-Installation setup for EMC VPLEX
- Pre-Installation setup for EMC XtremIO
- Pre-installation setup for FUJITSU ETERNUS Data Collector
- Pre-Installation setup for Hitachi Block
- Pre-Installation setup for Hitachi Block
- Prerequisites for adding Data Collectors (Hitachi Block)
- Installation overview (Hitachi Block Storage)
- Adding a Hitachi Block Storage Data Collector policy
- Configuring a Hitachi Device manager user
- Configuring a Collector for Hitachi NAS block storage
- Adding an HP command view advanced Data Collector policy
- Pre-Installation setup for Hitachi Content Platform (HCP)
- Pre-Installation setup for Hitachi Content Platform (HCP)
- Prerequisites for adding Data Collectors (Hitachi Content Platform)
- Installation overview (Hitachi Content Platform)
- Add a Hitachi Content Platform (HCP) Data Collector policy
- Setting up permissions for an HCP local user or active directory user
- Hitachi content platform system management console
- Hitachi content platform tenant management console
- Pre-Installation Setup for Hitachi NAS
- Pre-Installation Setup for Hitachi Vantara All-Flash and Hybrid Flash Storage
- Host inventory pre-installation setup
- Host Access Privileges, Sudo Commands, Ports, and WMI Proxy Requirements
- Host Inventory pre-installation setup
- Plan host Data Collection
- WMI Proxy requirements for Windows host Data Collection
- Host access requirements
- Verify command paths
- Host Inventory configuration steps
- Host Inventory setup overview
- Host Inventory maintenance overview
- Before discovering hosts
- Configure / Search the host Inventory
- Manage credentials
- Manage WMI proxy
- Manage paths
- Manage access control
- Host Inventory management
- Configure host Discovery policies to populate the host Inventory
- Execute and monitor host Discovery
- Validate host connectivity
- Show errors
- Filter the host Inventory - hide / un-hide, remove
- Host Inventory search and host Inventory export
- Export the host Inventory
- Configure and edit host probes
- Propagate Probe Settings: Copy Probes, Paste Probes
- Pre-Installation setup for HP 3PAR
- Pre-Installation setup for HP EVA
- Pre-Installation setup for HPE Nimble Storage
- Pre-Installation setup for Huawei OceanStor
- Pre-Installation setup for IBM Enterprise
- Pre-Installation setup for IBM COS
- Pre-Installation setup for IBM SVC
- Pre-Installation setup for IBM XIV
- Pre-Installation setup for Infinidat InfiniBox
- Pre-Installation setup for Infinidat InfiniGuard
- Pre-Installation setup for Microsoft Windows server
- Pre-Installation setup for NetApp-7
- Pre-Installation setup for NetApp StorageGRID
- Pre-Installation setup for NetApp Cluster
- Pre-Installation setup for NetApp E-Series
- Pre-Installation setup for Pure Storage FlashArray
- Pre-Installation setup for Veritas NetBackup appliance
- Installing the Data Collector software
- Introduction
- Installing the WMI Proxy service (Windows host resources only)
- Testing WMI connectivity
- Considerations to install Data Collector on non-English systems
- Install Data Collector Software on Windows
- Install Data Collector software on Linux
- Install Data Collector in containerized environment
- Validating Data Collection
- Uninstalling the Data Collector
- Manually starting the Data Collector
- Appendix A. Firewall configuration: Default ports
Probe settings
Table: Probe Settings
| Probe Type | Parameters | Description |
|---|---|---|
|
Capacity HBA iSCSI Volume Manager Multi-pathing Note: Do not enable HBA probes for VMware guest host collection. |
Probe schedule* |
A schedule in cron format; for example: */20 9-18 * * * which translates to "every 0, 20 and 40th minute past the 9, 10, 11, 12, 13, 14, 15, 16, 17 and 18th hour." |
|
Memory |
Probe schedule* |
A schedule in cron format; for example: */20 9-18 * * * which translates to "every 0, 20 and 40th minute past the 9, 10, 11, 12, 13, 14, 15, 16, 17 and 18th hour." |
|
Network |
Probe schedule* |
A schedule in cron format; for example: */20 9-18 * * * which translates to "every 0, 20 and 40th minute past the 9, 10, 11, 12, 13, 14, 15, 16, 17 and 18th hour." |
|
Process |
Probe schedule* |
A schedule in cron format; for example: */20 9-18 * * * which translates to "every 0, 20 and 40th minute past the 9, 10, 11, 12, 13, 14, 15, 16, 17 and 18th hour." |
|
Processor |
Probe schedule* |
A schedule in cron format; for example: */20 9-18 * * * which translates to "every 0, 20 and 40th minute past the 9, 10, 11, 12, 13, 14, 15, 16, 17 and 18th hour." |
|
System |
Probe schedule* |
A schedule in cron format; for example: */20 9-18 * * * which translates to "every 0, 20 and 40th minute past the 9, 10, 11, 12, 13, 14, 15, 16, 17 and 18th hour." |
|
Exchange |
Collect |
Check this box to activate collection on an on-going basis. When it is unchecked, only initial validation will attempt this probe. |
|
Probe schedule |
A schedule in cron format; for example: */20 9-18 * * * which translates to "every 0, 20 and 40th minute past the 9, 10, 11, 12, 13, 14, 15, 16, 17 and 18th hour." | |
|
Active Directory Host |
Host name or address | |
|
Active Directory Port |
For example: 389 | |
|
Active Directory Base DN* |
The starting point for the Active Directory. For example: CN=Services,CN=Configuration, DC=contoso2003,DC=com Several tools are available to help you identify the Base DN: - http://support.microsoft.com | |
|
Active Directory User Name |
Active Directory User Name This username must have privileges to search under the base DN within the Active Directory. Typically, this is an Administrator. | |
|
Password |
Active Directory Password | |
|
SQL Server |
Collect |
Check this box to activate collection on an on-going basis. When it is unchecked, only initial validation will attempt this probe. |
|
Probe schedule |
A schedule in cron format; for example: */20 9-18 * * * which translates to "every 0, 20 and 40th minute past the 9, 10, 11, 12, 13, 14, 15, 16, 17 and 18th hour." | |
|
Database* |
The name of the database within the SQL server. | |
|
Instance |
The system identifier to identify the SQL server database instance--for example: BKUPEXEC. Specify either an instance name or a port. If an instance name is not specified, MSSQLSERVER is substituted. | |
|
Port |
To identify the SQL server instance, provide either an instance name or a database port number; for example: 1433. If a port number is not specified, the port is determined automatically from the instance name. | |
|
Account* |
Database access user name The data collector requires a user account with permissions to execute the stored procedures | |
|
Password* |
Database access password | |
|
Windows Authentication |
Check this box if you want Windows authentication rather than SQL server authentication. | |
|
Oracle |
Collect |
Check this box to activate collection on an on-going basis. When it is unchecked, only initial validation will attempt this probe. |
|
Probe schedule |
A schedule in cron format; for example: */20 9-18 * * * which translates to "every 20 minutes between the hours of 9 a.m. and 6 p.m." | |
|
SID* |
The system identifier to identify the database instance. | |
|
Port* |
Database port number; default: 1521 | |
|
Username* |
The Oracle user must have the following role granted: SELECT_CATALOG_ROLE To grant this access, use: GRANT SELECT_CATALOG_ROLE TO 'user' where user is the database Username that you'll provide here. | |
|
Password* |
Database access password | |
|
Oracle ASM |
Collect |
Check this box to activate collection on an on-going basis. When it is unchecked, only initial validation will attempt this probe. |
|
Probe schedule |
A schedule in cron format; for example: */20 9-18 * * * which translates to "every 20 minutes between the hours of 9 a.m. and 6 p.m." | |
|
Account* |
The Oracle user privileges required: SYSDBA privilege if 10g sysasm in 11g | |
|
Password* |
Database access password | |
|
Port* |
Database port number; default: 1521 | |
|
ASM Instance* |
The name that identifies the database instance. | |
|
File Analytics |
Collect |
Check this box to activate collection on an on-going basis. When it is unchecked, only initial validation will attempt this probe. |
|
Probe schedule |
Default is once a month. A schedule in cron format; for example: */20 9-18 * * * which translates to "every 20 minutes between the hours of 9 a.m. and 6 p.m." |