Well, following the directions in the README you backed up certain directories first. Just restore those directories and restart the app server and you will be fine.
why do you want to do this?
you could just re-run the installer against the install, that should revert it, but there are db changes present w/ the hotfixes which may cause issues. it's not a re-install, the installer should 'repair' the install back to 115. though i would not reccomend this.
I wanted to know that as a precautionary measure, if at all hotfix installation fails in production infrastructure.
I agree to the fact that some of the hotfixes make changes to the DB as well, but if in case a hotfix is only changing bladelogic.jar and couple of other files, is it recommended to run the base installer again. My fileserver is hosted on the same machine and I can't afford even the risk of loosing around 10-15Gigs of depot objects..
Does running the installer again, only repairs the file or does it overwrites them??
1 of 1 people found this helpful
adam's comment about the backup restoration should be the best option. if you didn't do that, you should be able to apply the previous hotfix or do the re-install w/ the GA version. that will overwrite the files, though your config files should remain.
this is also why you should have a test/staging environment to test bladelogic hotfixes in.
Great thx Bill/Adam..
Yes we do have a replicated Sandpit for testing purpose..
This doesn't apply to BSARA hotfixes, does it? I tried re-running a hotfix after one was terminated mid-install and it looked like it just tried to re-install, not backout. Or does the hotfix have to completely install for the backout feature to work?