Page tree

Unsupported content

   

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

BMC TrueSight Capacity Optimization can help a storage administrator to manage storage capacity for storage arrays and filers.

Integration of performance and capacity data related to storage devices can be achieved by either integrating centralized storage management tools or by leveraging the Sentry Integrator for BMC TrueSight Capacity Optimization add-on (This option requires a separate license). For more information, see Market Zone Direct ETL modules and Sentry Software Integration documentation .

Mapping LUNs to vSphere VMFS datastores

It is possible to map LUNs to vSphere VMFS datastores thanks to a configuration metric VOLUME_EXTERNAL_ID defined in BMC TrueSight Capacity Optimization for this purpose. A relationship type called DS_USES_VOLUME is also available, and can be used to connect the two entities (datastore and volume).

For example, the Sentry Integrator for BMC TrueSight Capacity Optimization can load LUN's "naa" ID into VOLUME_EXTERNAL_ID. This requires the “volumes monitoring” option to be selected when configuring the ETL module is selected. Before activating this option (which may imply loading many entities into the BMC TrueSight Capacity Optimization database), ensure that you have sized the BMC TrueSight Capacity Optimization instance appropriately.

As mentioned in the vSphere section of the Managing Compute platforms topic, the vCenter Extractor Service also extracts this ID from the VMware API, and attaches it to the datastore entity. When these two strings match, the volume extracted at storage level is recognized as being the same identified as backing the datastore at hypervisor level.

For datastores backed by multiple extents (disk spanning), the DSTORE_DEVICE value contains only the first extent. But disk spanning is no longer recommended best practice because with VMFS5, a single LUN can be 64 TB.