6760 ServerNet/DA Manual

Migrating Data From a D-Series Release
6760 ServerNet/DA Manual—424879-003
D-5
If New System and Current System Are Dissimilar
If the current system is already running the D46.00 release, see the G-Series
Highlights and Migration Planning Guide for planning your migration.
If the current system is running a release that precedes D46.00, you should
migrate to D46.00 before you migrate your database to a NonStop S-series server
running the G06.01 or later release.
Migrating directly to the G06.nn release from any D-series release prior to the
D46.00 release is not recommended. Both the D46.00 and G06.01 releases
contain new Enscribe disk files and audit trails that are dissimilar to those in
previous releases. If you must fall back from the G06.01 release, your recovery
tasks will be simplified if you can fall back to the D46.00 release, which contains
Enscribe disk files and audit trails similar to those in G06.01.
Therefore, before you migrate to the G06.nn release from your NonStop K-series
server, you should install the D46.00, or later, release on that server.
If you are planning on migrating K-series external disks, you must be running at
least the D46.00 release; however, other important migration considerations might
also apply. For more information on migrating your K-series external disks, see the
G-Series Highlights and Migration Planning Guide.
For other detailed migration information, see the following documentation:
°
D4x.00 Installation Guide
°
D-Series System Migration Planning Guide
If New System and Current System Are Dissimilar
Will the new NonStop S-series system run in parallel with the current NonStop K-series
system? (This means the new system must have a unique node name and node
number.)
If so, this migration is likely to be very complex to implement, because you will
probably need to make modifications to database catalogs and file labels before
migrating the database. You should contact your service provider for assistance with
your migration.
When you move disk drives to a new system with a different node name and node
number, you must determine which database products installed on the current system
use the node name and node number to locate files. To migrate a database created or
managed by certain NonStop products requires special planning and modifications
before the database can be migrated successfully.
Data created and managed by the following products require special planning and
modification:
•
DSM/Tape Catalog
•
Enscribe
•
NonStop SQL/MP
•
NonStop Open Database Connectivity (ODBC) Server
•
NonStop Kernel Open System Services (OSS)