Migrating a multibos instance of AIX
If you previously ran the multibos command to create a standby BOS,
and restarted the system so that the standby BOS becomes the active BOS, and then removed the new
standby BOS, you are running the AIX® operating system in an
environment that does not have
hd10opt logical volumes, but instead the
bos_hd10opt logical volumes exist. Your system is
still recognized as a root volume group (rootvg) during an operating system installation, and the
logical volume names are changed to their original names during the migration (or preservation)
installation. If you use network alternate disk migration (nimadm command) to
perform the migration, the logical volume names are changed when you boot the
altinst_rootvg volume group created by the nimadm process for
the first time.
If you are running the operating system that has the
bos_* logical volumes (that
is, the bootinfo -v command returns
bos_hd5), but also have a
standby instance that has the original
hd* logical volume names, the standby
instance is treated as the rootvg during a migration or preservation installation, and the
bos_* logical volumes remain unchanged. If you want to migrate the instance that
bos_* logical volumes, remove the standby BOS by using the multibos
You must always back up your system before you migrate an operating system. Before you migrate, copy the usr/lpp/bos/pre_migration file from the media or from your network installation manager (NIM) Shared Product Object Tree (SPOT) of the level to which you are migrating, to a location on the target system. Run the file on the target system to check for any migration warnings.
bos_hd5logical volume. If this command returns 0.0, run the bosboot -ad /dev/ipldevice command to correct it, and run the blvset command again to verify the rootvg level. The command must return 6.1 or 7.1.
If you have both standby and active BOS on the system, remove the standby BOS. The originally
hd* logical volumes are treated as the operating system, whether it is
active or not.