The new BVQ Offline Scanner now also supports the new IBM SVC and Storwize Family Software Version 7.4
General support for the new 7.4 code will be available with BVQ Version 3.3.2 which we plan to make available this year.
If there are needs to do a performance analysis on a 7.4 code before the BVQ V3.3.2 becomes available, you may use the offline scanner and send us the data for analysis.
This scanner can now be used for all versions of IBM SVC and Storwize Family Software from V220.127.116.11 up to V7.4
W e... [More]
We are very proud to announce the general availability of BVQ Version 3.3.
BVQ Version 3.3 is the first IBM SVC and Storwize monitoring and analysis solution with full support of the IBM SVC and Storwize Family Software V7.3.x.
IBM SVC and Storwize Family Software V7.3.x enhances overall system performance by introducing a completely new cache architecture. With BVQ V3.3 we are now able to analyze this new cache architecture. This is highly essential, to better understand performance bottlenecks because many problem root causes can... [More]
The BVQ Storage reporting Service (SRS) is a solution which combines the strength of an onsite installed BVQ with the cost advantages of SaaS. SRS provides a very simple way for users to do storage monitoring by replacing time consuming monitoring steps with easy to understand reports. The SRS service is so sophisticated, that in case of unexpected performance problems a full BVQ analysis can be started immediately to quickly detect and fix any problems.
In many cases storage... [More]
Full support of the new SVC/Storwize Family 7.3
Version 3.3 will be an intermediate step , which we make available quickly, so that the new SVC / Storwize versions 7.3 can be analyzed .
With BVQ V3.3 we will support all SVC/Storwize code levels from 18.104.22.168 until the current 7.3.x .
The already available BVQ V 3.2 supports ... [More]
This is a a new performance analysis whitepaper in the technical section of BVQWIKI
The unbalanced VDisk mirror problem
Many performance issues are caused by an unbalanced situation in the two sides of VDisk mirrors.
One finds, that a mirrored Volume runs into latency peaks which cannot be explained by the Volume behavior itself. The managed disk groups (mdg) in the storage backend show completely different load and latencies.
We have recognized that often the distribution of primaries can cause this problem.
This is mainly interesting for IBM partners which want to use BVQ with their customers. We have an international partner program for BVQ. Please contact us at BVQ@sva.de or send a mail to Michael.firstname.lastname@example.org to ask for further details.
You can also use the contact form .
Storwize Family Software V7.3 has implemented many changes, specially in the cache architecture, Easy Tier and re-striping of storage pools. The changes target to enhance overall system performance. The experience is good but sometimes little things can cause trouble and can lead to a deterioration.
What to do, if you have made this experience?
Try to find the reason and fix it!
We have just released the new BVQ V3.3 offline scanner for general download. This scanner can now also capture the new performance metrics of... [More]
Next week we will first time show BVQ 3.3 Beta at the German SVC user group day in Ehningen.
BVQ version 3.3 supports the SVC / Storwize version 7.3 completely, including the new cache architecture.
Further improvements are removable window, with which more than an analysis can be edited at the same time.
Link to BVQ:
I am very proud about these kind of success stories, where we again could help a customer to solve a performance problem in shortest time.
Like this example:
2:30 pm we were informed by one of our sales colleagues, that the client has performance problems.
2:45 pm phone conference with the client starts
2:50 pm remote access to the BVQ on the client side established
2:50 pm Start of performance bottleneck analysis
3:15 pm we have clear indications, that the problem is not caused by the SVC. It is striking that... [More]
BVQ version 3.2 supports the new SVC / Storwize code versions 7.3.x
The BVQ scanner from older versions is not able to work with the new Storwize code.
New BVQ code Version 3.2
If you upgrade from BVQ versions before BVQ V3.0
Since BVQ 3.0 we also changed from DB2 V9.7 to DB2 V10.5. If you are still running DB2 V9.7 and you want to upgrade to BVQ 3.x you also need to upgrade to DB2 V10.5 and with this you need to have a new DB2 license file.
The special DB2 license is part of the... [More]
We have just released BVQ Version 3.2
Improved 'Look and Feel' of the GUI with customization possibilities and more space for content
More possibilities for searching, sorting and filtering functions in all tables
B etter analysis capabilities of environments with Easy Tier by using the new object type ' MDisk Tier '
Highlighting of individual curves in the performance view
Toleration support for code version 7.3, V7000 Gen 2 and DH8... [More]
Another new feature of the latest BVQ offline scanner allows to scan more than one systems at once.
This is especially helpful when you plan to use BVQ Copy Services Package to analyze Metro Mirror or Global Mirror connected systems.
A profile is created per Storage system, which is then used for this one system to separate the data. In this way, many different SVCs and or Storwize systems can be scanned at the same time.
Find more information here
The BVQ offline scanner has been updated . This scanner covers now also the SVC / Storwize code version 7.3 .
You can find the download and instructions for the offline scanner here .
BVQ Offline Scanner
Use BVQ to optimize SVC and Storwize in multi IO group clusters
Abstract (The whitepaper is in draft mode! )
The experience with the analysis of multi I/O group clusters always show the same kind of problem. Technical resources in larger SVC or Storwize environments are often utilized very unbalanced. This leads to performance bottlenecks in some areas of the system whilst other areas are totally underloaded. These kind of performance bottlenecks are often very hard to understand without using... [More]