NetBackup IT Analytics Data Collector Installation Guide for Virtualization Manager
- Pre-Installation setup for VMware
- Pre-Installation setup for IBM VIO
- Pre-Installation setup for IBM VIO
- Prerequisites for adding data collectors (IBM VIO)
- Installation overview (IBM VIO)
- Adding servers for the IBM VIO Data Collector policy
- VIO servers (IBM Virtual I/O Servers)
- LPAR clients (IBM Logical Partitioning Clients) managed by VIO servers
- HMC (IBM Hardware Management Console)
- Add an IBM VIO Data Collector policy
- Pre-Installation setup for Microsoft Hyper-V
- Install 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
- Uninstall the Data Collector
- Manually start the Data Collector
- Appendix A. Firewall configuration: Default ports
Configure VMware Access
The VMware Data Collector uses the VMware Infrastructure SDK and REST APIs over HTTPS to retrieve data from ESX servers. The VMware Data Collector is multi-threaded, enabling it to poll up to five vCenters in one polling cycle.
VMware requires the following access for data collection:
View-only VMware User ID that has a role with the following privileges:
Note:
Permissions can be granted to an existing local account or domain/AD user.
Assign the user to the root-level folder permissions of vSphere.
The administrator user who provisions the read-only role for collection must be an administrator at the root level, not just at a data center or other level. If multiple vCenters are available for administration in the client (Linked Mode), that administrator user must be provisioned at the root level for each vCenter Server from which data is collected.
Port 443 must be open. Data collection uses HTTPS without certificate validation for encrypted connections. This allows the use of a self-signed certificate on the VMware server.