GUI

Custom PI can't be calculated without any existing PI's

SVC Scanner

Exception caused by V7000-300 Node Ports, which just differ by type

DB Schema

Column "VM_SCSILUN_ID" in DDL Statement since Version 3.1 to short

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

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

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

SVC 6.2.0.3

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

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 VMware

Multiple 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 VMware

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

BVQ 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

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.

SVC 7.3
Performance Stats

Legacy VDisk cache statistics corrupted

SVC 7.3
Performance Stats

Node CPU core stats =0

SVC 7.3 Performance Stats

CPT, OPT, APT much too high

SVC 7.4 Performace Stats

CPU core COMP (compression) statistics too high (factor ~100).

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)