This topic provides information about BMC TrueSight Capacity Optimization configuration for collecting data directly from VMware environments using one of the following ETL tasks:
You cannot run the VMware - vCenter Extractor and VMware - vCenter and ESX Server History Extractor service simultaneously. To import historical data from vCenter and ESX servers you first need to start the VMware - vCenter and ESX Server History Extractor, then stop this service. Once the historical data is imported, start the VMware - vCenter Extractor service which continuously polls and collect data from vCenter servers.
BMC recommends that you use the VMware - vCenter Extractor Service ETL for data collection.
Use the VMware - vCenter and ESX Server History Extractor ETL for data recovery.
BMC TrueSight Capacity Optimization supports collecting data from the following VMware environments:
VMware - vCenter Extractor Service
VMware - vCenter and ESX Server History Extractor
VMware ESX Server 4.0, 4.1, 5.0, 6.0 (vSphere), and 6.5 (vSphere).
VMware vCenter Server 4.0, 4.1, 5.0, 5.1, 5.5, 6.0 (vSphere), and 6.5 (vSphere).
The VMware - vCenter and ESX Server History Extractor supports data collection from VMware ESX Server 3.5.
You can configure BMC TrueSight Capacity Optimization to collect data from a VMware environment by performing one of the following procedures:
For information about the metrics collected by the VMware ETL modules, see Metrics collected by VMware ETLs.
For information on the metrics collected at various logging levels (data collection levels) in VMware, see .
Duplicate entities of vCenter hosts or VMs in an entity catalog and private entity catalogs that contain duplicate vCenter entities are automatically identified by the VMware Automated Reconciliation task. You can reconcile and manage duplicate entities and sharing status of private entity catalogs according to your requirements.For more information, see the following topics: