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
- Deploy Data Collector in native Kubernetes environment
- Configure Data Collector manually for Veritas NetBackup
- Install Data Collector binaries on Windows (without configuration)
- Install Data Collector binaries on Linux host (without configuration)
- Validating data collection
- Uninstall the Data Collector
- Manually start the Data Collector
- Appendix A. Firewall configuration: Default ports
Datastore scan collection
By default, Inventory collection only captures information about the files referenced by a collected virtual machine (VM files), and only using the information available without directly contacting the datastore. Examples of large files that will not be collected during the default Inventory collection are .iso files (such as, DVD images) and disk images (.vmdk) that are not attached to any collected VM. Data collection runtime is reduced when using the default Inventory collection, but only files for VMs in the inventory are collected. Therefore, a considerable amount of consumed space in the datastore may not be captured. Choose the option to gain visibility into the storage that is not associated with a VM.
When you check , a more detailed collection is performed by scanning the datastore to discover files resident on the datastore, but not associated with a VM in the inventory. This option, although it may impact performance, finds files that may be invisible to VMware, but that are consuming space on the datastore. For example, a VM may have been removed without deleting files from the datastore. Similarly, log files or user-stored files may be taking up space not apparent from the VM inventory's perspective.
See Reports impacted by Datastore Collection.
Note:
If an error occurs during the Datastore Scan, then only the files available with the default Inventory collection will be collected for the Datastore. It is also possible that individual files may be found via the Inventory collection, but not via the Datastore Scan.