Table of Contents

Driven Migration Cookbook

version 1.1.1

This cookbook discusses how to migrate existing data from Driven Server version 1.0 to an upgraded Driven Server version 1.1.1.

The data migration process requires that you perform the following tasks in sequential order:

  • Back up your Driven Server 1.0 data

  • Install Driven 1.1

  • Check the status of your data

  • Perform the migration process

Back up your Driven Server 1.0

Refer to Implementing a backup strategy for your Driven Application chapter in the Driven Admin Guide for detailed information on backing up your data.

Install Driven 1.1

Refer to Installing the Driven Server chapter in the Driven Admin Guide to upgrade your server.

Note
 Once you have installed Driven 1.1 you will not be able to log into Driven until you complete the migration process.

Before migrating your data

The migration process is launched by using the Driven Client (Admin CLI Client) tool that communicates with the Driven Server. This CLI tool will kick-off a series of processes that will inspect and convert the integrity of your data. Therefore, before you begin, make sure that your Driven Client (Admin CLI Client) tool is the same version as the Driven Server.

Next, check the status of your data by entering the following CLI command in your Driven Client home directory:

driven reindex --status

If the response statement returns:

server reindex status: RUNNING_CURRENT

then you Do Not need to perform the migration process.

However, if the following statement returns:

server reindex status: REINDEX_NEEDED

then proceed with the migration process.

Note
 If the response statement is not one of the two mentioned, then either your Driven Server is partially upgraded or there is a mismatch of your Driven Server and Driven Client (Admin CLI Client). It is highly recommended that you contact Concurrent Technical Support before continuing with the migration process.

Performing the Migration Process

Once you have determined that your data needs to be migrated, perform the following tasks:

Step 1: Establish a console session with the Driven Server

You must establish a console session with the Driven Server. The migration process can last from several hours to an entire day, therefore it is highly recommended to use a screen session to establish communications with the Driven Server.

Note
 Contact Concurrent Technical Support if you have questions about establishing a screen session.

Step 2: Enter the CLI command to start the data migration process

Enter the following CLI command in your Driven Client home directory:

driven reindex --start

The Driven Admin CLI Client tool will manage the migration process by communicating with the server and kick-off subsequent processing steps in following order:

  • CREATE_NEW_INDEX

  • ENTITY

  • CASCADING

  • BINDING

  • CASCADING_DATA

Note
 The RUNNING_CURRENT status indicates that the migration process is complete.

Migrating Data from a remote Driven Server

You can start the migration process in a Driven Server by entering:

driven reindex --hosts http://some.driven.server --start

where some.driven.server is the URL for your Driven instance.

You must periodically check the output of the CLI reindex to view the status reporting of each migration process, which includes long steps of the cascading data reindex, geneology updates, and progress reports on how many records have been processed.

Example of CLI reindex output

******************
starting: CREATE_NEW_INDEX
status: 0 changes from 0 initial records done for CREATE_NEW_INDEX
finished CREATE_NEW_INDEX
******************
starting: ENTITY
status: 0 changes from 5 initial records done for ENTITY
status: 5 changes from 5 initial records done for ENTITY
finished ENTITY
******************
starting: CASCADING
status: 0 changes from 2059 initial records done for CASCADING
status: 0 changes from 2059 initial records done for CASCADING
status: 0 changes from 2059 initial records done for CASCADING
status: 2059 changes from 2059 initial records done for CASCADING
finished CASCADING
******************
starting: BINDING
status: 0 changes from 9 initial records done for BINDING
status: 9 changes from 9 initial records done for BINDING
finished BINDING
******************
starting: CASCADING_DATA
status: 9 changes from 9 initial records done for CASCADING_DATA
status: 700 changes from 9 initial records done for CASCADING_DATA
finished CASCADING_DATA

When the migration process is complete, the following output is displayed:

********************************************************
reindex done ( took 43 seconds ). server restart needed.
********************************************************

At this time, you can restart the Driven Server.