Content

Highlights

Bugfixes

New functions

None

Improvements

Issue ID

Module

Description

BVQ-9354

GUI

Objekt type 'Drive': various improvements

BVQ-9412

GUI

Topology view: ATS: Perf-aspects IO rate and data rate should also show the rates in TO

BVQ-9446

GUI

Topology view: enable path 'Controller port/MDisk tier'

BVQ-9433

GUI

Performance view: time-favorite: add 'Reset to default'

Bugfixes

Critical

Issue ID

Module

Description

BVQ-9457

DB Schema Migration

Load statements in 3.3.0.20, 3.3.3.3 break at TS pending backup on TSM backed DBs

Important

Issue ID

Module

Description

BVQ-9344

GUI

Object context menu: 'Drive' inactive for MDisk group

Issue ID

Module

Description

BVQ-9404

GUI

Topology view: aspect 'Capacity utilization': IO group & node don't show text overlay as 'CTX of abs'

Known problems

Issue ID

Module

Description

BVQBVQ GUI

Modifications in a GUI configuration file, regarding the scanner status checks, are necessary when a topology scanner interval > 30min is configured. Please contact the BVQ support in this case.

BVQBVQ Excel Export

The Excel-format generated by BVQ Reporting is compatible with Excel Version 2003 and higher.
The generated format is "XML spreadsheet 2003" (please see Microsoft article).
The default file extension for this format is :'.xml'. If it is saved as '.xls' however, a warning message will appear when opened with Excel.

BVQBVQ Scanner / Scheduler

New features for scanner or scheduler which were unlocked by a new license file will take effect after about 2 hours or after restart of the corresponding services.

IBM PMR 91765,033,724SVC 6.2.0.3Severe impairment of the VDisk latency by the SVC CLI command 'lsmdiskextent'. Seen at a cluster with 8 nodes (8G4) under 6.1.0.4.
Starting with BVQ 2.4.3 this command is not used anymore. Instead command 'Isvdiskextent' is used. 

IBM PMR
unknown

SVC 6.4.0.3

Massive accumulation of reaching the SVC limit of 10 simultaneously competitive SSH sessions can trigger a warm restart of the node.
Fixed with 6.4.1.3

BVQ-6610BVQ VMwareMultiple mappings of a VM virtual disk (and/or of different snapshot versions of a single VM) to a VM virtual machine are not supported yet.      
This happens for example with flash copy managers like TSM4VE. 
BVQ-6623BVQ VMwareScan and representation snapshots and thier capacities are not yet supported by BVQ. The 'Used Capacity' of a VM Virtual disk corresponds currently to the 'Used Capacity' of the original VMDK file.
BVQBVQ VMware

Currently not supported VMware functions:

  • Partitioned VM SCSI volumes, whose partitions are assigned to multiple VM datastores
  • VM SCSI volumes whose UUIDs are not unique
IBM PMR ?SVC Performance Stats

Starting with version 6.1.0.1  SLAV, PLAV and DLAV refer to the consolidated backend IO sizes of up to 256k. But not the IO-counter for CTRM and CTP, which means that their quotient may be too low by a factor of 8. Therefore, the VDisk below cache metrics SLAV and PLAV cannot be used directly to assess the backend latencies. Also their transaction size is not the same of the backend (max 32k).    

However, CTD was adapted to the consolidated IO sizes and provides continuously useful values.

IBM PMR ?SVC 7.3
Performance Stats
Legacy VDisk cache statistics corrupted
IBM PMR ?SVC 7.3
Performance Stats
Node CPU core stats =0
IBM Defect 197194

SVC 7.3 Performance Stats

CPT, OPT, APT much too high
IBM PMR ?SVC 7.4 Performace StatsCPU core COMP (compression) statistics too high (factor ~100).
IBM PMR ?SVC 7.3.0 Performance Stats
  • Legacy stats 'cm' and 'cv' are wrong (interchanged compared to the new stats 'm' and 'v')
  • Legacy stats 'ctr' and 'ctrs' show read misses instead of all reads (new stats 'r' and 'ri' are correct)

 

DB schema changes

Version
Tables
Description
3.3.0.20N/A(warning)* BVQ-9457: Hardened load statement by NONRECOVERABLE
3.3.3.3N/A(warning)* BVQ-9457: Hardened load statement by NONRECOVERABLE

Note: Depending on the required DB size of long-term processes, an increased temporary disk space is needed (see below).

Requirements and restrictions

Requirements of the HW/SW environment

Please see supported environments since BVQ 3.4

Minimum BVQ version required for an update

V2.7

DB2 advanced workgroup server edition version

10.5 FP5

Java Runtime minimum version1.8.0.45

More information

Please see release notes for BVQ V3.4.2  

 

Short description of the update steps

Important update notes

  1. BVQ licence: a new license file may be necessary to use certain new features.
  2. Temporary disk space: a few updates require the reorganization of the largest tables. Please make sure that at least additional 33% of the currently occupied capacity is available as free capacity in the DB file system. Depending on the DB size such schema migrations can take very long. Nevertheless, no measurement data is lost if the update procedure is kept.
  3. Permanent disk space: updates which store additional statistics usually need more permanent disk space for the database tables in the DB file system.
  4. GUI favorites:  during some of the GUI updates the predefined favorites are replaced. Possible custom changes will be lost. However, changes in user favorites remain .
  5. Update DB2 JRE: before installing the BVQ update please upgrade the system with the recommended DB2 and JRE versions.
  6. If you have problems: if something is going wrong, please contact your BVQ support partner.
  1. Preparations
    • Checking for correct function of the environment, in particular function of the scanner.
    • Manual stop of BVQ Scanner and Alerting-service, Scheduler-services and also of all GUIs and reporting-clients
    • Backup of BVQ installation directory and BVQ DB (e.g. DB offline backup with DB2 CMD, VMware snapshots) 
    • Starting again the BVQ Scanner
  2. Update BVQ Install Package Repository: bvq-package-repository-installer-x64-V3.4.2.exe
    1. DB Schema update
    2. BVQ GUI update
    3. BVQ Reporting Engine update
    4. BVQ Report Module update
    5. BVQ SVC Scanner update (warning)*
    6. BVQ VMware Scanner update
    7. BVQ Scheduler update
    8. BVQ Alerting update
  3. Performing functional tests
  4. If necessary inform colleagues about the need to update locally installed BVQ GUI / report clients. 

PDF Version

Page viewed times