Highlights
Bigfixes
New functions
none
Improvements
Issue ID | Modul | Description |
---|---|---|
BVQ-9917 | GUI | Performance-View: CPU: Tooltip and legend more descriptive |
BVQ-9942 | GUI | Cluster selection: Cluster ID column resizeable |
BVQ-9950 | GUI | FC mapping: Detailpane: Show "Bitmap IO group" |
Bugfixes
Critical
none
Important
Issue ID | Modul | Description |
---|---|---|
BVQ-9946 | SVC Scanner | Drive deletion doesn't clean the DRIVE table |
BVQ-9986 | GUI | CompressionCoreCount of a CG8 with 4 cores calculates a wrong value |
Recommended
none
Known Issues
Issue ID
Module
Description
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.
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.
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.
Starting with BVQ 2.4.3 this command is not used anymore. Instead command 'Isvdiskextent' is used.
IBM PMR
unknown
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
This happens for example with flash copy managers like TSM4VE.
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
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.
Performance Stats
Performance Stats
SVC 7.3 Performance Stats
See https://customercenter.sva.de/home/x/NwwgAw (support agreement needed to get access credentials)
DB schema changes
None
Requirements and restrictions
Requirements of the HW/SW environment | Please see supported environments since BVQ 3.5 |
---|---|
Minimum BVQ version required for an update | V2.7 |
DB2 Version | DB2 Advanced Workgroup Server Edition V10.5 FP5 |
Java Runtime minimum version | 1.8.0.45 |
More information | Please see Release Notes for BVQ V3.5.5 |
Short description of the update steps
Note | ||
---|---|---|
| ||
|
- 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
- Update BVQ Install Package Repository:
bvq-package-repository-installer-x64-V3.5.6.exe
- DB Schema update
- BVQ GUI update
- BVQ Reporting Engine update
- BVQ Report Module update
- BVQ SVC Scanner update
- BVQ VMware Scanner update
- BVQ Scheduler update
- BVQ Alerting update
- Performing functional tests
- If necessary inform colleagues about the need to update locally installed BVQ GUI / report clients.