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 930 times by 8 users since Dec 21, 2016


How-To install

Preparation of the operating system Windows

The following tests and adjustments should be made:

Action                                                              Short description
AdministratorMake sure that the installation of all components is performed by a user who is a member of the local user group 'administrators'.  
RestartsMake sure that the system can be restarted (several times) without any problems during the installation phase.     
Network connections
Disk storageSet up the necessary drives, paths and partitions to the recommended sizes as described in adjust disk storage configuration.
Minimize UACMinimize the Windows User Access Control configuration prior to the installation as recommended under: adjust user account control (UAC)
Customize virus scanner        If necessary, please customize the configuration of an installed virus scanner on the BVQ systems (see customize virus scanner)
Time and time zonePlease ensure that the clocks on all BVQ systems and other integrated systems are synchronized and set to the same time zone (please see check time and time zone) 
Windows userMake sure that the necessary conditions for Windows users are met. 

Additionally required software                    

Install the additionally required software on the BVQ systems
Contribution of BVQ license key files      Please ensure that your BVQ license key file is available in the download directory of your BVQ server. It will be needed for the BVQ installation.

Check and unlock network connections 

BVQ Services require the network connections to communicate with each other, with BVQ Clients and  the external disk- and VMware systems.    

(warning) Please adjust the settings of any existing firewalls accordingly.

(warning) Please check any necessary network connection by using ping.

Overview: possible network connection types

RDPMicrosoft Remote Desktop Protocol for remote screen sessions
SSHSecure Shell to access the SVC CLI
VMware WSWeb service with HTTPS on VMware vCenter API
MongoDB clientClient to access the MongoDB Service
InternetConnection to the Internet for remote maintenance or code-download
Overview: possible network connection types

Overview: Network connections

The following connections should or must be provided for each system:

Links / SystemStandard TCP portBVQ DB ServerBVQ ServerBVQ Client
RDP to client workstation3389(tick)(tick) ←(tick)
SSH to SVC22 (tick)(question)
WS to vCenter443 


MongoDB Client27017(tick)(tick)(tick)
Overview: Network connections

Legend: (tick) - nessesary connection, (question) - optional connection, → - outgoing connection, ← - incoming connection


Notes to Microsoft RDP

The GUI's operation on a BVQ server with the redirection of the screen display to a workstation by using Microsoft Remote Desktop Protocol (RDP) is supported, but is associated with a loss of image quality and speed. Therefore, we recommend to use the BVQ GUI screen directly without any diversion. In Windows 2008 Terminal Services environments certain settings have to be considered before installation starts (enable user installation mode).

Please see: 

(error) The cascading of two or more RDP sessions in a chain one after the other affects the display performance of the BVQ GUI enormously and is therefore not supported!


Adjust disk storage configuration

BVQ Services require a different amount of disk storage capacity at different times for program files, program data  and log files. For the approximately required capacity, please refer to the relevant document under BVQ supported environments.    

To ensure that in case of a problem overflowing directories does not endanger the execution of other services, we recommend to distribute main directories on multiple partitions or drives.       



  • At least for the MongoDB data directory an separate drive or a separate disk partition (typical D:) should be created on a fast SAN storage system.        
  • It is recommended to create the directory D:\bvq_downloads and to gather all necessary files for installation there.


The following main Windows directories are used to a significant degree:

Main directoryStandard pathTypical standard pathStandard driveUsage
Program files%PROGRAMFILES%\SVA\BVQC:\Program Files\SVA\BVQC:Storage of program files
Program data%PROGRAMDATA%\SVA\BVQC:\ProgramData\SVA\BVQC:Storage of service logs and queue data
Program files%PROGRAMFILES%\SVA\BVQ\bvq-mongodbC:\Program Files\SVA\BVQ\bvq-mongodbC:Storage of MongoDB program files
Program data%PROGRAMDATA%\SVA\BVQ\bvq-mongodbC:\ProgramData\SVA\BVQ\bvq-mongodbC:Storage of MongoDB database
Overview: BVQ main directories

A significant use can also be expected for the following main directories on each system:     

Directory / systemBVQ DB ServerBVQ ServerBVQ Client
Program files(tick)(tick)(tick)
Program data (tick)(tick)
MongoDB Database(tick)


Overview: main directories per system

Adjust User Account Control (UAC)

UAC - User Account Control Windows 2008 R2, 2012, Vista, 7, 8:

Microsoft introduced Windows Vista User Account Control (UAC) in Windows platforms to avoid that all actions are performed with administrator privileges.  

(warning) For the installation of BVQ components it is recommended to set the UAC temporarily to 'Never notify' (reboot required).     
When finished, it can be reseted to the previously set level. 


 How-To - Changes in the dialog 'UAC Manager'
  • Start UAC dialogue:
    • Either: start → execute/search field → enter: uac
    • Or: start → system control → path field → enter: system control\user accounts\user accounts → click 'Change settings of User Account Control'
  • Set control to lowest level 'Never notify'
  • After installation is finished reset control to original or desired value.

Customize virus scanner

(warning)  During the installation of BVQ disable any virus scanner or other programs which vary from the basis Windows installation and might interfere with the installation.

The virus scanner on the BVQ server should be set so that the following directories are NOT searched:

Database Directory

Note: Problems has been observed in context with the virus scanner 'Sophos', which could be relevant for others too.

Check time and time zone

The time and time zone of the BVQ systems have to be set properly.

(warning) Please check whether a NTP server is configured in Windows: it is strongly recommended to use a NTP server to synchronize all clocks of all systems (SVC nodes, Windows) .

(warning) Please check whether the time zone is set correctly: the time zone of all systems (SVC, Windows) have to be set to the same value.

Check Windows user

Locally managed user

The following users and groups are created during the BVQ installation on the BVQ server. This chapter does not contain any adjustments to be carried out here and just provides an overview.   

(info) Often the username 'BVQ' is shared for the BVQ Service and DB user. In this case, the name of the BVQ Server may not be 'BVQ' as both the server and the user name are managed in the same Windows namespace .

TypeNameMember ofDescription
User accountbvqLocal administratorsBVQ user account (Access and create the database, updates bvq database, BVQ Windows services)
User account (optional)bvqservice BVQ Windows services run under this user account


User managed by active directory

If a domain registration is used, the database and the BVQ User must be created in advance on the AD server.
The following table provides an overview of the required users and their user groups in active directory.



Member of


User account


Domain user, local administrators

BVQ user (Access and create the database, updates bvq database, BVQ Windows services)


Additional required software

The following overview shows which software is required on the BVQ systems:

Software / SystemBVQ DB ServerBVQ ServerBVQ Client
Java Runtime Environment (tick)(tick)
PuTTY (question)(question)
PDF Reader (question)(question)
Remote Screenshare(question)(question)(question)
Overview: additionally required software per system

Legend: (tick) - required software, (question) - optional software


BVQ installation packages

Download files

Please download the following software from the Internet on the BVQ ServerBVQ installer


Java Runtime Environment (JRE)

An Oracle Java Runtime Environment version 1.8.x with most current patches has to be installed on the BVQ server, database server and the clients.

Java 32/64 bit version

The Java Runtime Enviroment 32/64 bit version has to match the bit version of the operation System (not the Browser)

As the Browser is usually running as 32-Bit version the auto download on the will download the wrong 32-Bit version. Please select your appropriate version from the manual download page:


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

Check your java settings
:: Show current Java Version
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)

PuTTY (optional)

PuTTY is an optionally required free Secure Shell (SSH) terminal console. It is used to perform commands in the SVC CLI  .

Usually PuTTY is installed  on the BVQ Server and, if necessary, also on the client workstations. 

In a BVQ environment the following added values are offered with the installation and configuration of PuTTY:        

  1. PuTTY allows independent assessment of the SVC connections on the BVQ server and, if necessary, also the test or adaptation of SVC parameters.
  2. The pogram PuTTYgen  allows the user to create a SSH private/public key pairs, which may be needed for the configuration of the BVQ Scanner.
  3. A user may use pre-configured PuTTY sessions from the BVQ GUI, to adjust the configuration of SVC resources (see also Cluster CLI scripts).

For a working call out of the  BVQ GUI the following configuration steps have to be executed: 

(warning) Please attach the PuTTY directory  to the system search path %PATH% an (typically: ;C:\PROGRA~2\PuTTY ).

Can be configured in computer → properties advanced system settings Advanced → environment variables → user variables→ path

(warning) Please create a PuTTY session for each SVC / Storwize cluster  with the same name as the cluster (from lssystem name,  please note upper / lower case).

The following parameters have to be defined in PuTTY to connect to an SVC Cluster:

    • Category: session
      • Host name (or IP address) = IP address or DNS entry for the relevant SVC cluster 
      • Port = 22
      • Connection type = SSH
      • Saved sessions = name ot the relevant SVC Cluster
    • Category: connection -> aata
      • Auto-login username = bvq
    • Category: connection -> SSH -> auth
    • Back to category: session
      • Click button 'save' in order to store settings permanently

During the first connection the error message that the SSH fingerprint has not been saved in the registry can occur. This has to be confirmed once with 'Yes'.

Remote Screenshare (optional)                          

If you grant the BVQ support team a controlled access to a screen session on your BVQ systems, support for you and the BVQ team is greatly simplified. Answers for questions or errors can be found much faster and unnecessary back and forth sending of e-mails is avoided.

We recommend the installation ofl the software 'TeamViewer' on one or more BVQ systems which have access to the Internet. As a result, you can enable the BVQ support to work together with you on the local screen. TeamViewer can be downloaded from the Internet with the following link:

Some companies prohibit communication with the TeamViewer server (in Germany) by a firewall. In this case please contact your network administrator.

IBM SVC / Storwize systems

The following checks and adjustments should be made to the SVC / Storwize systems:

ActionShort Description
Configuration of SVC userPlease create a user account (typically 'bvq') within the group 'Administrators'.
Check SSH access for free sessionsPlease check whether 2 SSH sessions are free on each involved system in order to ensure communication with the BVQ SVC scanners.
Check time and time zonePlease check whether an NTP server and the same time zone are set on each involved system as well as on the  BVQ systems.
Check performance statistics intervalPlease check the settings of the performance statistics  on each involved system (default: 5 minutes).

Configuration of SVC user

For the communication of the BVQ SVC Scanner with the SVC CLI a user account on each SVC is mandatory, which should be at least member of the group 'Administrator'.

(warning) Please create such a user. We recommend that to give that user the following name: bvq

The user authentication can be done via SSH key pair and in recent SVC/Storwize code versions also via password.
The configuration of a user with password authentication is easier. For SSH key authentication  an SSH key pair has to be generated initially.

  • Creation of an SVC user with password for BVQ with SVC CLI:

    svctask mkuser -name bvq -usergrp Administrator -password P@ssw0rd

  • Creation of the BVQ user with SVC Web GUI:
    1. Please Browse with a web browser to the following URL: https://<cluster ip address>/gui#users-users
    2. Log in with a user in the group SecurityAdmin (superuser)
    3. Click on 'Create User" and fill in the following dialogue as following:

    4. If you have chosen an authentication via SSH key pair, you can upload the public key in this dialogue.


*Unfortunately, the performance monitoring of an SVC / Storwize cluster without the permission level 'Administrator' is not possible so far as for copying the performance statistics files from the other nodes into the config node the CLI command svctask cpdumps is mandatory. This is the only administrator-level command, which uses the BVQ SVC scanner. For all other commands (svcinfo lsxxx) the permission level 'monitor' would be sufficient. 

Check SSH access for free sessions

The number of simultaneously opened SSH sessions is limited in the SVC/Storwize to 10 sessions for SVC Code < 7.5. If the sessions are used by other applications, it should be ensured that for a short time up to 2 SSH sessions are simultaneously required for the communication with the BVQ SVC Scanner.

Check time and time zone

The time and the time zone of the SVC/Storwize systems have to be set correctly.

(warning) Please check if an NTP server is configured: we strongly recommend to use an NTP server to synchronize the time of all systems (SVC Nodes, Windows). 

CLI command for setting an NTP server:
svctask chcluster -ntpip <IP address of NTP Server> ### Example: svctask chcluster -ntpip

(warning) Please check whether the time zone is set correctlythe time zoneof all systems (SVC, Windows) should be set to the same value. 

CLI command for setting the time zone (here Europe/Berlin):
svctask settimezone -timezone 360 ### Timezone 360: Europe/Berlin !!!

(warning) At the end please check  whether  the expected time is actually displayed.

CLI command for showing the cluster time:
svqueryclock ### Check the cluster's current date and time

(info) If previously no NTP server has been configured , it is not advisable to delete the old performance statistics of all nodes at once because it is not certain that it they were created at the same time on each node.

CLI command for deleting asynchronous statistic-files if necessary:
svctask startstats -interval 5 && svcinfo lsnode -nohdr | while read id rest ; do svctask cleardumps -prefix /dumps/iostats $id ; done


Check performance statistics interval

The SVC performance statistics are generated regularly (in intervals) by the SVC and picked up by the BVQ SVC Scanner. BVQ supports all intervals possible in the SVC (1min to 60min).

We recommend to set the time interval to 5 minutes. If a closer monitoring should be necessary, the interval can also be reduced to 1 minute.

(warning) Please check the interval time set in the SVC / Storwize. Example:

svcinfo lssystem | while read key value; do [[ "$key" =~ ^(statistics_status|statistics_frequency)$ ]] && echo "$key $value"; done
statistics_status on
statistics_frequency 5

 (warning) If necessary, set the interval time to 5 minutes:

svctask startstats -interval 5 ### Set SVC Perf Statistics Interval (possible values 1-60)

Configure unified Storwize V7000

The V7000u system consists of 2 levels:

  1. The upper level provides a file service gateway (file nodes)
  2. The lower level consists of a V7000 (storage nodes)

The administration of a V7000u is usually done by using the IP addresses of the file service gateways. CLI commands are tunneled through that layer to the underlying V7000. Unfortunately, the performance statistics of the V7000 cannot be downloaded from this upper level . Hence cluster IP addresses have to be assigned to the underlying V7000.

(warning) Check whether a cluster IP address is set there on the V7000u:

cluster_id       cluster_name location port_id IP_address   subnet_mask   gateway       IP_address_6 prefix_6 gateway_6
00000200A080006A swv1blk      local    1
00000200A080006A swv1blk      local    2

(warning) If necessary, set a cluster IP address on the V7000u:

chsystemip -clusterip -gw -mask -port 1

Similar to a usual V7000 the BVQ SVC Scanner has be configured  to access this IP address.

Create SSH key pair (optional)

 How-To - Create a SSH key with PuTTY for SVC authentication

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'.


VMware vCenter systems

VMware vCenter user

For the operation of BVQ VMware Scanner, a user is required for the operation of the BVQ VMware Scanner, who should at least have read-only access to the VMware vCenter system.

(warning) Please create this user before installing the VMware BVQ Scanner. We recommend to name the user as follows: 'bvq'




Pre installation checklist


  • No labels