By now you should have read HACWS migration strategy and planned your HACWS migration strategy. If you have not done this, you should read the section now. Refer to the items in this section as you implement your HACWS migration strategy.
Before you begin your HACWS migration, you should back up the root volume group on each control workstation, and you should also back up the shared volume group which contains the /spdata file system. If anything goes wrong with your HACWS migration, you can recover by restoring the appropriate backup images. If you separate your HACWS migration into multiple service windows, then you should backup your HACWS configuration each time, in order to make sure the backup images are current.
You may back up the root volume group by issuing the mksysb command directly, or you may invoke the mksysb command through SMIT by issuing the command smit mksysb. You may back up the shared volume group which contains the /spdata file system by issuing the savevg command directly, or you may invoke the savevg command through SMIT by issuing the command smit savevg. Refer to the AIX documentation for more detailed instructions.
Before you can migrate your HACWS control workstations to |PSSP 3.4, |you must migrate to AIX 4.3.3. Migrating the control workstation to PSSP 3.4 describes |two different methods for upgrading AIX on a non-HACWS control workstation. You should upgrade AIX on an HACWS control workstation by either applying AIX PTF service, if this is possible, or performing a migration install of AIX. Refer to the AIX Installation Guide for AIX installation instructions. If you perform a migration install of AIX, verify that any changes that were made to /etc/rc.net on the backup control workstation during Step 31: Add IP address aliases do not get lost. These changes should be preserved by the AIX migration installation, but if they are not, they will need to be re-created in order for your HACWS configuration to work correctly.
Once you have completed the installation procedure, you should verify the migration of AIX by running the following command:
oslevel
The output of this command is the current AIX software level. If you are not at the level you expected, you can also use this command to get a list of file sets that need to be updated. For example, to find out which file sets must be updated in order to reach AIX 4.3.3, issue the following command:
oslevel -l 4.3.3.0
You may need to install AIX PTFs in order to migrate those file sets to the desired AIX software level.
Whenever you make a significant change to your HACWS configuration, such as upgrading the AIX software level, you should always run the HACMP clverify utility to verify the HACMP cluster upon which your HACWS configuration is based. You should resolve any problems that clverify reports before you consider the AIX upgrade to be successful. However, if you are going to upgrade HACMP immediately after you upgrade AIX, then it makes sense to delay running clverify until after you upgrade HACMP. Refer to the "Verifying cluster software" and "Verifying the cluster topology" chapters of the HACMP for AIX: Installation Guide for more information about this utility.
In addition, you can use the hacws_verify command to check for
problems with your HACWS configuration. You will be asked to run this
command when you upgrade PSSP. However, if you upgrade AIX and then put
your HACWS configuration back into production before you migrate to |PSSP 3.4, then you should run this command after you start control
workstation services on the primary control workstation.
| If using: | Do this: |
|---|---|
| SMIT |
|
| hacws_verify | Enter:
/usr/sbin/hacws/hacws_verify |
Before you can migrate your HACWS control workstations to |PSSP 3.4, you must install any level of HACMP that is supported with the level of AIX that you are using with |PSSP 3.4. Refer to the "Upgrading an HACMP cluster" chapter of the HACMP for AIX: Installation Guide for HACMP migration installation instructions.
After you upgrade HACMP on both control workstations, you should run the HACMP clverify utility to verify the HACMP cluster upon which your HACWS configuration is based. You should resolve any problems that clverify reports before you consider the HACMP upgrade to be successful. Refer to the "Verifying cluster software" and "Verifying the cluster topology" chapters of the HACMP for AIX: Installation Guide for more information about this utility.
After you upgrade HACMP on both control workstations, you need to identify
to HACMP the HACMP pre- and post-event scripts that are provided by
HACWS.
| If using: | Do this: |
|---|---|
| SMIT |
|
| spcw_addevents | Enter:
/usr/sbin/hacws/spcw_addevents |
You already performed this task, when you originally installed HACWS. However, a new release of HACMP may introduce more cluster events, so you need to repeat this task, so that HACWS-supplied pre- and post-event scripts get defined to HACMP for the newly introduced cluster events. Failure to do this will not hurt the functionality of your HACWS configuration, but it will cause the hacws_verify command to fail.
In addition to the HACMP clverify utility, you can use the
hacws_verify command to check for problems with your HACWS
configuration. You will be asked to run this command when you upgrade
PSSP. However, if you upgrade HACMP and then put your HACWS
configuration back into production before you migrate to |PSSP 3.4, you should run the command after you start control workstation
services on the primary control workstation.
| If using: | Do this: |
|---|---|
| SMIT |
|
| hacws_verify | Enter:
/usr/sbin/hacws/hacws_verify |
|Proceed to Migrating an HACWS configuration to PSSP 3.4.