AIX

 View Only

 LKU Liveupdate AIX

Jump to  Best Answer
Houas MENASRIA's profile image
Houas MENASRIA posted Thu October 30, 2025 06:21 AM

Hello team,

First, I successfully updated AIX from 7.2TL5SP7 to 7.2TL5SP9

However many questions marks subsiste.

I assigned 2 more disks for LKU,hidisk1 should contain alternative disk (clone of hdisk0) and hdisk2 to surrogate disk (mirror rootvg from hdisk0 taken to new created partition).

After success KLU, I have the alternative disk shown as lvup_rootvg as beow.

hdisk0 00ccf8a79c868f32 rootvg active

hdisk1 00ccf8a7653b8f65 lvup_rootvg

hdisk2 00ccf8a716488169 None

This disk "hdisk1" can be used to rollback ? the answer is no. 

 I changed bootlist to boot from hdisk1 but disk unbootable !!! how ? it should boot to rollback right ?

Another questions, if I have efixes to install after update, how can I proceed, making another LKU or is the anoterway to include during LKU ?

I used geninstall function during this try. ( I tried to upgrade with nim server but the upgrade was on the initial disk ??? even I put hdisk1 and hdisk2 on liveupdate.data on nim and on the lpar ???)

Thanks in advance to clarify me above questions;

Kind regards,

Houas

Thanks to Chris and Christian for your answer. I folllowed boths your documentations to test Live update. What I understood the rootvg is mirrored on mhdisk and the update happened on nhdisk (serrogate) then at the end of live update, original rootvg updated, mdisk can be used to roll back?

What I remark, on my test, the update start updating rootvg first, then clone disk on nhdisk (serrogate), the mirrorvg on mhdisk ?

Here my config

$lspv

hdisk0          00ccf8a79c868f32                    rootvg          active
hdisk1          00ccf8a7653b8f65                    None
hdisk2          00ccf8a716488169                    None

my lvupdate.template

.....
general:
        kext_check = yes
 
disks:
        nhdisk  = hdisk1
        mhdisk  = hdisk2
        tohdisk =
        tshdisk =
 
hmc:
        lpar_id  =
        management_console = hmcdev
        user = hscroot

Chris Gibson's profile image
Chris Gibson  Best Answer

After a Live Update, the disk specified as nhdisk (hdisk1 in your case) contains the rootvg volume group that was used to boot the surrogate LPAR. This volume group was created by copying the original LPAR rootvg volume group but t contains only a minimal AIX image. It can't be used to roll-back. The lvup_rootvg volume group cannot be unconfigured. This is because it contains the rootvg volume group that was used to boot the surrogate LPAR and to provide the chroot environment into which the processes from the original LPAR were migrated. This disk cannot be removed from the partition, or used for any other purpose, until the partition is rebooted or another Live Update operation is performed (using another, different disk for nhdisk).

It is considered best practice to create an alternate rootvg backup (with alt_disk_copy) to another disk before starting a Live Update operation. Please review some of the AIX Live Update Best Practices here: http://gibsonnet.net/blog/cgaix.backup.Oct.2024/resource/chris_aix_live_update_best_practice_v0.8.pdf

Christian Sonnemans's profile image
Christian Sonnemans IBM Champion

Hello Hounas,

Indeed please read the answer of Chris, I will post within a few weeks also the session 1194 that we held at the TechXchange 2025 Orlando. So during that session I explained that I always start with creating an alt_disk_copy first as fall-back disk.