With the release of BVQ 5.2 we provide a possibility to migrate your existing BVQ DB2 database to the new MongoDB backend. Based on your specific use case you can choose between multiple migration options.

 

If your license is valid you don't need a new one during the migration

Get in touch with us!

The Migration itself is an easy step by step procedure. But to find the best level of granularity and migration mode we strongly recommend to in contact. We will assist you and make the procedure as easy as possible!
bvq@sva.de 

 Download Migration Tool


Background

 

 Why do we need a migration?

Since BVQ version 5.1 we had to drop our database backend based on IBM DB2. The database was replaced with the NoSQL Database "MongoDB". Have a look into the release notes of version 5.1 (BVQ Release notes 5.1).

To keep your existing data we have to migrate this data into the new database and the new structure.

 What does the migration tool do?

The migration tool is responsible to read your data form the DB2 Database and write it into the new MongoDB correctly. To do so it will execute the following tasks:

  1. Provide an Interface to select the data you want to migrate
  2. Read the data from the DB2
  3. Cleanup some historical bugs if needed
  4. Transform the data into the new structure
  5. Write the data into MongoDB

The migration will generally take part in the following order:

  1. Topology (Current)
  2. Eventlog
  3. Scannerlog
  4. Toplology history
  5. Performance indicators
  6. Performance values
 How long does the migration take?

 The duration for a migration is difficult to determine. It depends on the level of migrated data, database size and system performance. The migration of performance data will take the most time.

Level of migrated data

We grouped the amount of data that will migrated into three packages that are usefull. They vary in terms what data will be migrated. What settings has to be made in the migration tool for each package is visible in the settings screenshot below.
Generally you can adjust the settings according to your own needs but it is strongly recommended.

Minimal


Migrate only the current Topology without Performance Data and Topology History

(plus) Advantage

  • Fastest possible Migration
  • Minor system load
  • Start with a clean new database (no historical bugs, etc.)

(minus) Drawback

  • No capacity charting for values previous to migration
  • No performance values previous to migration
     

 Basic


Migrate the current Topology and the Topology History. No Performance Data is migrated.
 

(plus) Advantage

  • Capacity charts are still available

(minus) Drawback

  • No performance values previous to migration
  • Depending on the Historical Topology size, higher system load and longer migration process

 


 Complete (Recommended)


Migrate all data from DB2 to MongoDB. (Current Topology, Topology History, Performance Data)
 

(plus) Advantage

  • All data available after migration immediately

(minus) Drawback

  • High utilization of system resources
  • Long migration process (depending on DB size)

 


Split your migration process

If you prefer you can also split your migration. Start with a Basic Migration and fill the performance data in a separate run with just the Performance Values checked.

 

Migration Mode

Single Host


All involved migration components (DB2, MongoDB, Migrator, BVQ-Services) will run on a single host.

(plus) Advantage

  • Easy to get started
  • No need to configure a separate host
  • Minimum network load

(minus) Drawback

  • Slower than Host to Host migration
  • Competing resource utilization
  • Higher resource requirements for CPU, RAM, Disk performance and Disk space
  • No opportunity to run BVQ for MongoDB and DB2 on the same host

 

 

Host to Host


The migration components can be spread on two different hosts. Resources can be used more economic.

(plus) Advantage

  • Much faster than Single Host Migration
  • Less resource requirements for CPU, RAM, Disk performance and Disk space
  • Opportunity to run both systems in parallel and no need to migrate all data
  • Easy to drop DB2 instance after migration or just keep it as archive

(minus) Drawback

  • Necessity to setup a new host with network connectivity to DB2 instance
  • Additional network load as all Data has to be transferred by LAN

Step by Step 

Single HostHost to Host

Prepare your environment

  • Take a snapshot of your current VM
  • Update your system to version 5.0.1, 5.0.2 or 5.0.3
  • Extend your free storage capacity for the new database
    • Depending of the condition of your DB2 DB we expect the MongoDB Database to be much smaller than DB2.
    • To be safe, provide the same space for MongoDB as your actual DB uses
    • We recommend to use a separate partition to be more flexible
  • Extend the RAM and CPU resources for the VM during the migration process
    • We recommend to double both. It can be reduced after the migration is finished.

DB2 Host

  • Update your system to version 5.0.1, 5.0.2 or 5.0.3
  • Nothing more to do yet

MongoDB Host

    • Follow the BVQ installation Pre-requisistes to prepare the new VM


Install BVQ with MongoDB

  1. Download the latest BVQ repository installer: BVQ 5.2
  2. Download the Migration Tool: (see link at top of document)
  3. Follow the BVQ installation manual. Stop/Pause right at the beginning of GUI Installation!
  1. Download the latest BVQ repository installer to the MongoDB Host: BVQ 5.2
  2. Download the Migration Tool to the DB2 Host: (see link at top of document)
  3. Follow the BVQ installation manual. Stop/Pause right at the beginning of GUI Installation!


Run the Migration Tool

  1. (warning) Stop all BVQ Services
  2. Start the Migration Tool
  3. Enter all details to connect to your local DB2 Database
  4. Next
  5. Enter all details to connect to your local MongoDB Database. You set up these during the installation process.
  6. Select the data you want to migrate.
  7. Start migration
  8. Wait until the migrator will tell you to start your services
  9. Resume the installation you paused after the GUI Setup
  1. (warning) Stop all BVQ Services on the DB2 Host
  2. Start the Migration Tool on the DB2 Host
  3. Enter all details to connect to your local DB2 Database
  4. Next
  5. Enter all details to connect to the remote MongoDB Database. You set up these during the installation process. Make sure the firewall port is opened.
  6. Select the data you want to migrate.
  7. Start migration
  8. Wait until the migrator will tell you to start your services
  9. Resume the installation on the MongoDB Host you paused after the GUI Setup
  10. If Migration has finished you can start the services on the DB2 Host to have two running BVQ systems

 

 

Video - How-to migrate

  • No labels