Quote:
Originally Posted by
itik
[...]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.