Red Hat Bugzilla – Bug 535427
Add "backup" and "rollback" functionality for JBoss CP upgrades
Last modified: 2014-05-05 16:56:21 EDT
This came about after discussions with a customer after an EAP 4.3 CP_03 > CP_04 that went wrong and prevented the target EAP servers from starting[1][2]. If they had not been wise and tested on a few non-production servers, the failed upgrade would have broken all ~200 of their deployed JBoss servers. In the manual CP upgrade instructions, we stress that the target JBoss instance be backed up prior to starting the upgrade. It only makes sense to try and follow this procedure during an upgrade from JON. Is this feasible? [1]https://enterprise.redhat.com/issue-tracker/302025 [2]https://enterprise.redhat.com/issue-tracker/298056
Ok, looks like I was mistaken, ran across this while doing a CP upgrade: # Package: JBoss EAP 4.3.0.GA_CP04 4.3.0.GA_CP04 # The following steps were provided by the plugin. They describe the steps that will take place during the deployment of this package. Please review the steps before deciding whether or not to continue with the deployment. Step Number Description 1 Download file from the server and save it to [#{downloadFolder}/#{software.filename}]. 1 Calculate the digest of [#{downloadFolder}/#{software.filename}] using the [MD5] algorithm and check it matches [#{software.MD5}]. 1 Unzip [#{downloadFolder}/#{software.filename}] into [#{patchFolder}]. 1 Carry out [stopIfRunning] action on the server. 1 Backup and replace [#{jbossServerHomeDir}/deploy/management/console-mgr.sar/web-console.war/applet.jar]. 1 Backup and replace [#{jbossServerHomeDir}/deploy/management/console-mgr.sar/console-mgr-classes.jar]. <snip>
Right Mark, we backup all files which get updated by the CP process, but the restore is still a manual process.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2123
mass add of key word FutureFeature to help track
Triaged 20-Dec