Of course this is possible - this is exactly what the product is for in first place:
The multibos command allows the root level administrator to create multiple instances of AIX on the same rootvg. The multibos setup operation creates a standby Base Operating System (BOS) that boots from a distinct boot logical volume (BLV). This creates two bootable sets of BOS on a given rootvg. The administrator can boot from either instance of BOS by specifying the respective BLV as an argument to the bootlist command or using system firmware boot operations.
These are the first three sentences from the first paragraph fom the first source everybody should consult - the manpage.
I do not like to say that, but: the forum can help you but it will not do the understanding for you. You are a long-standing member here and should really know by now.
[...]How do I restore previous state if my current update failed w/o multibos? Is that possible?[...]
That depends on what you did. As you did not give a proper description on what that was I assume that you did sth. like a smitty update_all. In this case there is a build in parachute in installp that will allow you to return to the previous software levels. To pull the ripcord you did tell the update not to commit but to apply and keep the older packages. This way you could simply reject all packages that are applied but not commited.
Occasionally some packages are commited automatically even if you told installp to apply only. This would be the case if new filesets came with the update packages. However, as such a fileset has not been there before the update operation you could uninstall it.
Now what to do if the software was commited during update? In that case you might try to do a forced overwrite with the previous/older versions. But be warned: this is not supported officially and does not always work. You might end up with a server with inconsistent software levels. I'd not recommend it for servers that are critical for production.
Last resort: recover the server from the backup you did before updating. Depending on the possibilities you have this might be the fastest way to return to the previous oslevel anyway.
I want to remove commands having no output. In below text file.
bash-3.2$ cat abc_do_it.txt
grpg10so>show trunk group all status
grpg11so>show trunk group all status
grpg12so>show trunk group all status
GCPKNYAIGT73IMO 1440 1345 0 0 94 0 0 INSERVICE 93% 0%... (4 Replies)
I am still working on my mksysb restore.
My latest issue is during an alt_disk_install from tape I got the following error after all the data had been restored.
0505-143 alt_disk_install: Unable to match mksysb level 5.2.0 with any
available boot images. Please correct this... (0 Replies)
Is multibos really needed on each sp update on a hacmp config?
Is someone using it?
I have an up coming update and I don't have time to understand this technology. Does SP update might screw you up and you can't restore properly from it?
Thanks for any idea in advance. (1 Reply)