BVQ version 5.3 introduces a new scanner infrastructure for SVC, Storwize and VMware systems. See: BVQ 5.3 Release notes

Comparison

New Scanner (>5.3)

The new scanner module is now consolidated into a single windows service by default ("bvq-scanner-local"). Its only purpose is to collect the information from all configured system and store them into the file system. Configurations for each system to scan are stored in the BVQ database and are managed via the BVQ Server Web UI. The BVQ Server is responsible for persisting all data into the database.

(plus) Advantages

  • Much lower resource utilization
  • Much easier configuration management - even without Remote Desktop Connection
  • Much simpler installation process
  • One scanner for all systems (SVC/Storwize & VMware)

(minus) Drawbacks

  • SSH-Keys for SVC/Storwize authentication not supported any longer due to security issues
  • Additional migrating step to setup the scanned systems

 

 

Old Scanners (<5.3)

BVQ was shipped with separate scanners for SVC/Storwize and VMware. For each scanned system a dedicated windows service was started with at least 512MB RAM consumption. Nearly all configuration settings had to be set during the installation process and were stored on the file system. The scanner instance was responsible for collecting all data from the system and for storing them in the database.
 

(plus) Advantages

  • both SVC/Storwize authentication methods are supported (SSH-key authentication or password)
  • Well known concept in BVQ history

(minus) Drawback

  • A lot of resource overhead because of multiple windows services
  • Difficult to modify configurations or delete a single scanner instance
  • Limited number of instances supported
  • Complex and error-prone installation process
  • Coupling to database problematic in many use cases

Split your migration process

It is possible to run the old scanner type and the new scanner type at the same time, as long as no system is scanned by BOTH scanners.

Note

BVQ 5.4: The old scanner types will be removed from the BVQ repository installer but will be available as separate installers to update existing setups.

BVQ 5.5: The old scanner types will no longer be supported.

 

 

Migration Options

Full MigrationIncremental Migration
(warning) Due to the database migration that might take some hours no data will be collected from svc or vmware clusters and might result in a small gap in performance data. If this is unacceptable please use the incremental migration!

The Incremental Migration splits the update process into two steps.

1. Step: Update to BVQ Version 5.3 including switch to the new scanner architecture
2. Step: Update to BVQ Version 5.4. During the long-term migration, the previously installed scanner (Step 1) buffers the data in the filesystem.
    After the migration is complete the data is written to the database

Prepare your environment

  1. Change the "bvq"-user on all SVC/Storwize systems to use password authentication instead of SSH-key.
  2. Stop all BVQ Services (except Mongo DB and Server services)
  3. Backup your scanner configurations
    • C:\Program Files\SVA\BVQ\bvq-svc-scanner\conf
    • C:\Program Files\SVA\BVQ\bvq-vmware-scanner\conf

  4.  Perform the Install BVQ - the latest BVQ version, following the instructions. After installation is done, it is important you perform this check:

    • Check that all new scanner work fine (Last result = success and performance data shown in GUI)
      Note: In large environments, the results of the first scan may not be visible for up to an hour.

5. If everything works fine,  uninstall BVQ SVC Scanner & BVQ VMware Scanner Module using the Windows control center deinstall  or double-clicking uninstall.exe in each modules home-directory

    1. Change the "bvq"-user on all SVC/Storwize systems to use password authentication instead of SSH-key.
  2. Stop all BVQ Services
  3. Backup your scanner configurations
    • C:\Program Files\SVA\BVQ\bvq-svc-scanner\conf
    • C:\Program Files\SVA\BVQ\bvq-vmware-scanner\conf

Install BVQ the latest BVQ version (incl. MongoDB)

  1. Download the latest BVQ repository installer: BVQ 5.4
  2. Run the repository installer as administrator
  3. In the module selection dialog check the BVQ MongoDB, BVQ Server, GUI and Alerter (optional)
  4. Make sure the "Skip Screens and use existing values" checkbox is unchecked
  5. Follow the installation instructions

 

  1. Download the BVQ repository installer: BVQ 5.3
  2. Run the repository installer as administrator
  3. In the module selection dialog check the BVQ Server and check SVC Scanner and VMware Scanner
  4. Make sure the "Skip Screens and use existing values" checkbox is unchecked
  5. Follow the installation instructions until the SVC Scanner or VMware Scanner setup appears
  6. Proceed with the installation
  7. After the installation all scanner instances should be up and running

Setup the new scanner

Follow the BVQ-Scanner Setup instructions - BVQ Installation Repository Installer
  1. Open a browser (Internet Explorer 11 or older isn't supported) and visit the BVQ Web UI (http://localhost)
  2. Navigate to the scanner overview
  3. Open Windows "Services"
  4. Stop and Deactivate all scanner instances
  5. Switch to the web browser and add all scanner instances
  6. Fill in all fields and save


  7. Check that all new scanner work fine (Last result = success and performance data shown in GUI)
    Note: In large environments, the results of the first scan may not be visible for up to an hour.
  8. If everything works fine, deinstall bvq-svc-scanner using Windows "Programs and Features"
  9. Download the latest BVQ repository installer: BVQ 5.4
  10. Run the repository installer as administrator
  11. In the module selection dialog check the BVQ MongoDB, BVQ Server, GUI and Alerter (optinal)
  12. Make sure the "Skip Screens and use existing values" checkbox is unchecked
  13. Follow the installation instructions

 

 

Video - How-to

Will be available soon

  • No labels