Migration from HACMP/XD for HAGEO to PowerHA SystemMirror Enterprise Edition, GLVM Configuration
The objective of this white paper is to help existing HACMP/XD for HAGEO customers understand how to plan for and accomplish a successful migration to the GLVM configuration of PowerHA SystemMirror Enterprise Edition.
HACMP/XD for HAGEO (hereafter referred to as “HAGEO”) has been maintained but not significantly enhanced for the last several years. The last HACMP/XD release to support HAGEO is 5.4.1 and that support is currently scheduled to terminate at the end of 2011. With the 5.5 release, the GLVM configuration of PowerHA SystemMirror Enterprise Edition (hereafter referred to as “GLVM”) provides IP-based replication function which is essentially equivalent to HAGEO but also provides significant improvements in usability, reliability and integration with AIX (see the “Overview of GLVM” section of this paper for details). HAGEO customers are encouraged to move to GLVM to take advantage of these improvements in GLVM as well as other improvements in PowerHA. This white paper provides information and examples which they can use to create their own detailed plan to successfully accomplish that migration.
This white paper provides an overview of the HAGEO and GLVM technologies and compares their technical workings as well as their external interfaces. The requirements for both HAGEO and GLVM are reviewed. The different HAGEO mirroring configurations (sync, mwc and async) are briefly reviewed and mapped to the mirroring configurations available in GLVM (sync and async). Migration prerequisites are presented along with the steps required before actually starting the migration process. The actual migration steps for two sample configurations (one with synchronous mirroring and another with asynchronous mirroring) are presented in detail. A summary section is provided at the end of the white paper.
The HAGEO user intending to move to GLVM should read through this paper to understand the concepts and techniques used to migrate two different configurations. The user should then develop an individual step-by-step migration plan that best suits his/her specific configuration and situation.