NonStop NS-Series Database Migration Guide

Preparing to Migrate to an Integrity NonStop
NS-Series System
HP Integrity NonStop NS-Series Database Migration Guide—540469-001
1-9
Phased Migration Versus Rapid Migration
Phased Migration Versus Rapid Migration
Phased migration and rapid migration are examples of two contrasting database
migration strategies.
Table 1-4. Criteria for Developing a Database Migration Strategy
Criteria Relevance
How important is round-the-clock
business continuity and
database availability?
The more important it is to avoid or minimize database
downtime and protect applications and data, the greater
the likelihood that you will choose a migration strategy
that uses online data movement tools to migrate
manageable subsets of the database for thorough
testing and validation on the new system.
How large and complex is your
SQL/MP or SQL/MX database?
The larger and more complex the database, the greater
the need for online data movement tools to minimize
downtime.
Do you simultaneously maintain
duplicate copies of your
production database on one or
more systems?
If you maintain duplicate copies of your production
database on one or more NonStop S-series systems,
you assume a significantly lower risk if you migrate the
database than you would migrating without duplicate
copies. If problems occur during migration from the
primary database, another copy of the production
system automatically takes over and keeps the
database running without interruption.
How fast can data be migrated
over your Expand network?
The time required to move data over a network depends
on the network’s speed and bandwidth. If your network
is slow and speed of data movement is important for
migration, you might want to upgrade your network
through reconfiguration and possibly the addition of new
equipment.
Is most of your migrated data
static or dynamic?
A database with large amounts of dynamic data
changes faster and more significantly than a database
with large amounts static data. Migrating a dynamic
database calls for a reliable, high-performance online
database replication tool such as RDF or one of its
third-party equivalents.
Are you committed to performing
and completing database
migration in a relatively short
time?
If you are committed to performing and completing your
database migration in a short time (hours or days), your
migration strategy might be limited to one that allows for
rapid database migration.
Are you willing to make
significant investments in time,
resources, and equipment to
maximize the performance and
reliability of your new database?
If, for example, you want to validate your database
migration procedures and database configuration on a
QA or test system before you migrate the database to
the new production system, you would need to acquire
the hardware and software to support both systems.