click to expand ...

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



Recent Version



VersionReleasedInstall Packages in oneGUI GUI GUI 




Table of content



This release does not support upgrade installs. We will provide support for migration from older BVQ releases based on IBM DB2 very soon. In urgent cases migration can be requested on demand. Do not hesitate to contact our BVQ support team in case.


All Version 5.0 Features

BVQ 5.0

Mongo DB support

Starting with this version, we support a modern NoSQL type DB called "Mongo DB" as the DB back end for all BVQ services. The use of IBM DB2 is now deprecated and will only be supported for existing installations by a limited time frame. New BVQ installations will only be supported with this Mongo DB back end. Upcoming releases with features and bug fixes will exclusively be available for Mongo DB BVQ installations.

Why did we do that?

Four summarized answers to that:

  • More modern NoSQL concept
  • More performance and scalability
  • Self-adaptive schema
  • Integrated installer

Mongo DB is based on a more modern NoSQL DB concept compared to a relational DB system like IBM DB2. Due to our experience, it is much faster for reading and writing huge amounts of less structured data like statistical measurements from a high number of concurrent measuring points. Most of the transaction processing is done in memory, so this is much faster too. Its compression is better, so data needs less disk space to be stored. Due to the fact that Mongo DB is a document typed NoSQL DB, it does no longer need complex schema migrations which simplifies adding new attributes or statistical metrics. The small MongoDB package (~110 MiB) is integrated in our BVQ standard installers. This puts the complete process under control of a single BVQ install-package and eases installs or upgrades a lot. Due to all this advantages of Mongo DB, we are much more scalable and cost efficient and are able to broaden support for much larger, multi-platform environments.

Current restrictions

Mongo DB is a NoSQL DB, therefor it does not support SQL selects. If you use customized SQL select statements for reporting purposes, you can change them to Mongo DB queries. The DB Schema is only changed as less as possible compared to DB2. We are currently working on a new web based reporting service, also providing a RESTful interface to all known BVQ information. This will present all information as available in the BVQ GUI to any requesting application. So this will be a much more powerful and stable way to get data out from BVQ as easy and flexible as possible. With this version we dropped support for the BVQ Reporting module based on Eclipse BIRT.

This release is only intended for new installs and does not support upgrades from IBM DB2 based BVQ versions. We will provide such an upgrade support very soon (planned Q1 2017) to enable existing customers to migrate to Mongo DB seamlessly.


Requirements of the HW/SW environment

Please see Supported Environments

Minimum BVQ version required for an update

Upgrades will be supported later

Minimum Mongo DB Version


Recommended Java Runtime version


 Version 5.1

Version 5.1

New features

Issue ID



BVQ-10752DBAdd support for Mongo DB back end


Issue ID



Bug fixes


Issue ID





 Version 5.1.1

Version 5.1.1

New features

Issue ID



BVQ-11083CommonSVC Code 7.8 toleration support


Issue ID



BVQ-11509GUIFavorites: Be able to sort sequence inside a folder with drag & drop
BVQ-11599GUITreemap: Legend: Path should reflect filter settings

Bug fixes


Issue ID



CriticalBVQ-11731SVC ScannerIllegalStateException: "Got more than 1 latest Hist entry for given PKs" in EasyTier enviroments
CriticalBVQ-11744InstallerError if DB dependency checkbox is unchecked
CriticalBVQ-11695GUIFavorites: Sometimes data loss of info texts or config settings
ImportantBVQ-11688GUIFavorites: NPE after dragging System folder into User Folder
ImportantBVQ-11343GUIScanner status: Topology persist is sometimes in WARN state because of "Unable to parse speed [NONE]" warning



 Version 5.1.2

Version 5.1.2


Issue ID



BVQ-11747InstallerMongoDB: Simplify user creation process
BVQ-11747ScannerTopology Persist: Cleanup after failed persist


Bug fixes


Issue ID



CriticalBVQ-11793GUITreemap/Table: Virtual maschines missing in Path: /BVQ/Cluster/MDisk group/VDisk/VM Vm
CriticalBVQ-11749CommonDatabase dependent services sometimes fail to start
CriticalBVQ-11800InstallerInstall pathes for MongoDB not taken for all pathes
ImportantBVQ-11775GUISearch by date strings in TopologyView broken with MongoDB





Page viewed 350 times by 8 users since Dec 21, 2016

For the usage of BVQ, the provided environment has to meet certain requirements. Please ensure that the following requirements are met for the server, client and network!

Hardware requirements

  • The stated minimum requirements allow operation in an environment depending on the number of volumes.
    Please ask back for sites larger than 8000 volumes.

SVC/V7000 supported software versions

Please take a look at this page:  Supported SVC software environments


  • Most installations are carried out on a VMware guest system.
    During production the following setups should be planned for different sizes.

Number of volumes





< 1000

3GHz, 4 cores


120GB free


1000 - 4000

3GHz, 4 cores


250GB free


4000 - 8000

3GHz, 6 cores


500GB free


Supported operating systems

The following table lists which operating systems are supported for servers and clients.

Operating system (English/German)

BVQ server

BVQ client workstation (GUI)

Windows Server 2012, 2012 R2,
64 Bit, (English / German+ current patches)



Windows Server 2008 (>=SP1), 2008 R2,
64 Bit, (English / German+ current patches)



Windows Server 2003 R2 SP2, 64 Bit



Windows 8, 8.1 (+current patches) (tick)

Windows 7 SP1, 64 Bit (+current patches)



Windows Vista SP 1, 64 Bit (+current patches)



In addition, the following conditions have to be met:

  • (warning) The name of the host / the server (s) (especially BVQ DB server or their combinations) MAY NOT BE BVQ! (otherwise the required BVQ user on the system can not be created!)

  • The time and time zone of the BVQ server must be equal to the time of the monitored SVC cluster. Here NTP is recommended for automated configuration time.
  • The BVQ server (BVQ DB server / server BVQ / BVQ GUI), needs the LAN side of the split port 50000 for communication between server / GUI and DB to be unlocked and accessible.
  • For communication between the server and BVQ to monitor SVC clusters, the port 22 has to be open for SSH or SCP or accessible.


Software pre-requisites

DB2 Advanced Workgroup Server Edition

IBM DB2 AWSE version 10.5 fix pack 5 is required on the database server.

The OEM license needed for installation is included in BVQ and therefore does not need to be purchased separately.

An overview of the latest version can be obtained at:
In the section # DB2 installation, a detailed step by step manual for installing DB2 can be found.

Java Runtime Environment (JRE)

An Oracle Java Runtime Environment version 1.8.x with most current patches should to be installed on the BVQ server, database server and the clients.
(warning) The Java Runtime Environment 32/64 bit version must match the bit version of the operating system!

The installed version of Java and the Java file association can be checked by using the following commands:

C:\>java -version
java version "1.8.0_xx"
Java(TM) SE Runtime Environment (build 1.8.0_xx)
Java HotSpot(TM) 64-Bit Server VM (build xx, mixed mode)

C:\>C:\WINDOWS\SYSTEM32\java.exe -version
java version "1.8.0_xx"
Java(TM) SE Runtime Environment (build 1.8.0_xx)
Java HotSpot(TM) 64-Bit Server VM (build xx, mixed mode)

C:\>assoc .jar

C:\>ftype jarfile
jarfile="C:\Program Files\Java\jre6\bin\javaw.exe" -jar "%1" %*


PuTTY is a free Secure Shell (SSH) client. It allows to send direct commands via a terminal session to the SVC CLI. PuTTY is required during installation of BVQ to check the following SVC parameters and to adapt them if necessary:

Create a SSH-key

For mutual authentication between SVC and PuTTY, an SSH-key is needed. The creation of an SSH-key is described in the following section:

Download PuTTY (puttygen.exe) from the following website:
Then execute puttygen.exe:

  1. Accept the parameters SSH-2 RSA and number of bits in a generated key: 1024.
  2. Select 'Generate'. Then move the cursor over the popup window to the button 'Key is fully created'.
  3. The 'Key passphrase' and 'Confirm passphrase' have only to be entered, if the private key has to be additionally protected by passphrase.
  4. Select 'Save public key'. Enter a file name with the extension .pub (for example: and then save the file in a separate directory: eg * \ SSH_Key_SVC.
  5. Select 'Save private key'.

  6. Click 'Yes'. This confirms that you want to save the key without a passphrase.
    Then enter the file name with the extension of .ppk (eg: SVCClusterName_Username.ppk). Save the file in the same folder as the public key.
  7. Close the PuTTY key generator.

Upload public key in SVC

The key can be assigned to the SVC GUI to an existing user. Alternatively, a new SVC user for BVQ can be created.

1. Call the SVC GUI and authenticate as Security Admin or Superuser.
2. Select 'User Management' -> User.
3. Add the SSH public key to a new or existing users.
(warning) The SSH key user must be in the user group 'Security admin' or 'Admin'.

[BVQ> prerequisites> svc_sshkey.PNG]


Adobe Acrobat compatible reader

The included BVQ reports are created as PDF files by default. To view them a PDF reader is required.
The Adobe Acrobat Reader software can be downloaded from the Internet at the following link:

TeamViewer or Cisco WEBEX for support purposes

The BVQ team prefers the software 'TeamViewer' for world wide remote support. TeamViewer can be installed on the BVQ server (or as workaround on security issues on any work station with RDP access to the BVQ server).
The TeamViewer software can be downloaded at the following link:

TeamViewer is our preferred tool but remote access can also be instantiated with many other methods.

SVC Storwize settings

SSH access

  • SSH and SCP access to SVC/V7000 cluster using SSH key

  • 2 unused SSH login sessions per SVC cluster and server BVQ


SVC time synchronization


Before starting the scanning services on the affected SVC clusters, the following actions have to be performed:

  • Ensure the correct SVC cluster time and time zone (eg: Europe / Berlin, UTC ...)
    This should be automated via NTP.

  • (warning) Important! The scanner scans at 1.4 attempts performance matched to the time of delivery of SVC data.
    This requires that the clocks on the BVQ servers and SVC nodes are synchronized!

  • The best way to ensure this is achieved by using NTP:
    • BVQ scanner system: Time Synchronization with NTP Server option
    • SVC / Storwize cluster: Time synchronization with NTP Server option.

CLI procedure:

### Set Timezone and NTP ###
svctask settimezone -timezone 360             ### Timezone 360: Europe/Berlin !!!
svctask chcluster -ntpip <IP adress of NTP Server> ### Example: svctask chcluster -ntpip


SVC performance statistics interval

The SVC performance data is copied at regular intervals by BVQ scanner into the BVQ database. To achieve this BVQ requires a solid SVC performance statistics interval of 5 minutes.

  • Check whether old remnants of 'iostat' files on the SVC clusters exist and delete them if necessary (SVC GUI - \> list dumps ...)
  • SVC perf statistics enable tracing in 5min intervals (BVQ version 3 will also be able to support 1 min intervals)

CLI procedure:

### Sweep and start Perfstats ###
svctask stopstats
svcinfo lsnode  -nohdr | while read id rest ; do svctask cleardumps -prefix /dumps/iostats $id ; done
svctask startstats -interval 5

Other conditions

Active directory - Domain registration

(warning) If a domain registration is used, the database and the BVQ users have to be created in advance as described in active directory domains registration.

The following table provides an overview of the required users and their user groups in active directory.


UAC - User Access Control Windows 2008 R2 / Vista / Windows 7

Starting with Windows Vista Microsoft introduced the User Access Control (UAC) on the Windows platform. The intention was to avoid that all actions are performed with administrator privileges.

For the duration of the BVQ SW-installation, it may be necessary to set the UAC to 'Never notify' (reboot needed!).

When the installation is finished UAC can be resetted to the previous level.

UAC manager:

  • Start -> execute ... -> uac
  • To install set control to "Never notify".

  • Reset after a successful installation to the original value.

SSH connection

For communication between SVC and BVQ a Secure Shell (SSH) connection is required. For this purpose the BVQ SSH / telnet client PuTTY is used in addition.

The following parameters must be defined in PuTTY for connecting to a SVC cluster:

  • Category: session
    Hostname (or IP address) = IP address or DNS entry of the appropriate SVC cluster
    Port = 22
    Connection type = SSH
    Saved sessions = enter name of the corresponding SVC cluster

  • Category: connection -> data
    Auto-login username = bvq

  • Category: connection -> SSH -> auth
    Private key file for authentication = off # SSH key created select 'Create. Ppk file'

  • Back to category: session
    Save button to save settings permanently


(info) On first connection attempt an error message may appear that the SSH fingerprint is not saved in the registry. Confirm this warning once.

BVQ GUI remote desktop with Microsoft RDP

The redirection of the BVQ GUI-operation from a server to a workstation by using Microsoft Remote Desktop Protocol (RDP) is supported. But losses in rendering quality and speed must be expected.
Therefore, it is recommended to use GUI to BVQ screen directly without detours.
In Windows 2008 Terminal Services environments certain settings need to be considered before installing (in user mode enable installation).
Please follow this link for more information:

Adjustment of virus scanner on the BVQ server

The following directories should not be scanned!


Problematic behavior has been observed in connection with the virus scanner from Sopohs. This can potentially be also relevant for other virus scanners.

Pre installation checklist