click to expand ...

Home
About SVA ... Contact us
Overview (all documents)
Product description
Services with BVQ
BVQ advantages
New functions and future plans
White papers
Downloads and releases
Users Manual and users guide
Further WIKI documents
Performance analysis and monitoring for IBM SVC and Storwize

 




Name of Solution:
Business Volume Qualicision (BVQ)
BVQ VMware Integration Package




Brief Description
The VMware Integration Package connects the SVC / Storwize storage objects with the VMware Storage objects. The VMware objects are imported and integrated with an own scanner in the BVQ- Database. Therewith, a collective presentation and monitoring of both areas is enabled. The storage usage and status of single VMs of the objects are displayed and there exists a very swift possibility to determine, which SVC areas provide storage for a virtual machine. Latter is especially then interesting, when performance problems in VMware have to be analyzed. In this case, there are only few actions to find the SVC/Storwize volumes that have to be analyzed.

Description of the Solution
The VMware Integration Package applies an own scanner in order to read the following object- types out of the VMware vCenter, to store them into the BVQ-database.
VM vCenter, VM Datacenter, VM Cluster, VM Host, VM SCSI Volume, VM Datastore, VM Datastore cluster, VM Virtual Disk, VM Virtual Machine


Image. 1: The new BVQ Objects that integrated through the VMware Integration Package. These objects are then available in the BVQ-Database and can be presented in the BVQ Treemap, in context with the SVC/Storwize objects.


Through this complete integration, there now is the possibility to clarify certain questions, such as, which VMware machines utilize which SVC Volume, or in the case of a performance bottleneck in VMware, which Volume is responsible for this bottleneck (Images 2, 3).
However, the VMware objects in BVQ are constructed as a complete topology of the vCenter, up to the VM Virtual Machine that can also be analyzed without SVC/Storwize objects in the Treemap (Image 4).
The VMware objects can also be evaluated with the BVQ- storage efficiency-analysis methods. Statements about the current efficiency of the VMware internal Thin Provisioning are therefore possible (Image 5).


Image 2: VMware Objects and SVC/Storwize storage objects in the Treemap are connected. The SVC/Storwize objects (Cluster, Managed Disk Group und Volume) are displayed in green, and the VMware Objects /here VM Virtual Machines) in purple. On this picture one can see the connections of VM virtual disks, VM Data stores and their relative space-requirements in the Volumes and Managed Disk Groups.


Image 3: In this example, you can see the VDisks that provide individual VM virtual machines with memory. The VM virtual machines are ordered by capacity. When a performance problem in a VMWare virtual machine occurs, a targeted SVC Volume analysis can now be launched very swiftly. Even very small VM virtual machines can easily be found by using the search function. (This picture is displayed unsharply, because the data originate from the client database)



Image 4: The VMware Integration Package reads the storage-relevant information from the vCenter and displays it in the BVQ. Thereby, information is depicted, that does not directly relate to the SVC or Storwize System. In this picture you can view VM SCSI volumes, which have a connection to the SVC (the selected providing SVC volume in green color) and other VM SCSI Volumes, which are provided by another storage system (no green SVC object in the VM SCSI Volume).



Image 5: BVQ analyzes the current efficiency of the VMware Thin Provisioning.VMware objects such as VM-Disks with large profit through the Thin Provisioning are marked with blue and green. If the Thin Provisioning still does not illustrate any single- price remuneration for VMware objects, these will then be marked with yellow or red.

Particular Views are deposited in the BVQ database.They enable the data usage for further analyzing systems. A connection to the BVQ database can be quite easily built up via the standard-protocols like ODBC or JDBC. The construction of the views is publicly documented.

Licensing for BVQ VM Integration Package
The BVQ VM Integration Package is licensed, depending on SVC/Storwize System:

  • BVQ Base Edition for IBM SAN Volume Controller Licensing on the bases of capacities in the SVC
  • BVQ Base Edition for IBM Storwize V7000 Licensing on the bases of V7000 Enclosures
  • BVQ Base Edition for IBM Storwize V3700 Licensing on the bases of V3700 Systems (one license per system)
  • Hybrid forms of SVC and Storwize Products Specific License on demand in order to avoid Double-Licensing


More specific on the BVQ Websites

 

 

  • No labels