Chris’s AIX Live Update Best PracticesThe official IBM AIX Live Update Best Practices are well documented here:
Best practices for the Live Update function
Please refer to these when planning a Live Update implementation in your environment.
I have written about my experiences with Live Update numerous times.
AIX Live Updates http
How to Live Update Your AIX System Without Rebooting the Server
AIX Live Update in a PowerVC Managed Cloud http
I’ve been testing and working with Live Updates over the last couple of years (since 2015). What follows are some of my “best practices”, based on my experiences using this tool in the field. They are not official IBM best practices and should be treated as such. These are merely guidelines, based on anecdotal data I have collected whilst using the tool. I hope you find them useful. I’ll update this page as I discover new items to add (or remove from) this list.
Chris’s AIX Live Update Best Practices for 2019! |
Hi
Jorge, yes, at a minmum, two disks are required for the actual live
update process. And a third is (optionally) required for the clone of
rootvg (should you choose to create one. Which you should because it's a
great way to back-out. You should create the alt disk copy before you
apply any fixes and/or start the live update operation). If you have
paging and/or dump devices outside of rootvg, then you will need
additional (temporary) disks for the live update process.
"If
paging space is present on a non-rootvg disk, or if a memory dump device
is present on the non-rootvg disks, two sets of disks must be provided
(one set for the original partition and another set for the surrogate
partition) with enough capacity for these paging spaces and memory dump
devices. The preview mode of the Live Update operation can compute the
required amount of space. These disks are available for reuse when the
Live Update operation completes."
https://www.ibm.com/support/knowledgecenter/ssw_aix_72/com.ibm.aix.install/lvupdate_configuration.htm
From the live update /var/adm/ras/liveupdate/lvupdate.template file:
# tohdisk = <disk1,disk2,...> The names of disks to be used as temporary
# storage for the Original. This is only required if the Original
# is using paging space or dump devices on non-rootvg volume groups. The
# capacity needs to match the total capacity of paging spaces and dump
# devices defined on non-rootvg volume groups for the original
# partition. (If previewing, size checking will be performed.)
# tshdisk = <disk1,disk2,...> The names of disks to be used as temporary
# storage for the Surrogate. This is only required if the Original is
# using paging space or dump devices on non-rootvg volume groups. It
# must have the same capacity as tohdisk. (If previewing, size checking
# will be performed.)
Thanks for this document Chris.
As
I am new to Live Update, I'm a bit lost when it comes to applying new
TL/SP levels... In addition to the two disks required by Live Update
(I'm using HMCs), the clone of the OS done prior to the update then
requires a 3rd disk? Or am I missing something here?
Cheers