26 - Migrating to TruCluster Server

Abstract

Migrating from TruCluster Production Server or TruCluster Available Server version 1.[56] to TruCluster Server version 5.X is a fairly significant task since it is not possible to perform a “rolling” upgrade. In fact, it is not possible to have a V1.[56] cluster connected to a V5.X cluster. Things covered in this chapter belong to migration assessment, migration tools, migration options, migration examples, and migration benefits. Some of the migration planning include the number of systems in the current cluster, the current version of the OS and TruCluster, presence of any additional PCI slot, acceptable downtime for migration, types of ASE services being used, and non-requirement of old-style DRD services. There are four primary scripts that are of great help to migrate from V1.[56] to V5.X clusters. These scripts are part of the TruCluster Server kit found on the Tru64 UNIX Associated Products CD (Volume 2). The specific subset name is TCRMIGRATE5xx. While migrating a V1.[56] cluster to V5.X when a rolling upgrade cannot be performed and it is not possible to have the V5.X cluster connected to the V1.[56] cluster, there are only three options from which to choose that are usually thought of as a trade-off between downtime and expense. It is advisable to install TruCluster Server on newly installed V5.X system. Also, partitioning disks for the cluster-common file systems is a must. Testing CAA sources, gathering configuration data, and applying the configuration data are necessary steps in this migration. While there are multiple benefits of migration, if the migration fails then reconnecting the production data back to the V1.[56] cluster and booting the V1.[56] cluster are vital.