Having been through the nightmares of upgrading a remedy server several time here are the things to consider:
1. Make sure you do this in a lower environment and test, test test. There may be bugs in the patch. Never count on a server patch to be 100% bug free. I have been bit by this one several times. 2. Make sure and back up any cusomizations you have done to remedy base forms -- they usually start with "AR System". The "AR System Email Messages" form is a specific one that comes to mind. 3. Don't forget to backup any customizations you have made to mid-tier web pages (login.jsp, lougout.jsp come to mind). 4. Make backups of your ar.conf, armonitor.conf, your license file (since you are on 7.1 not needed), and arsystem files just in case. 5. Don't forget to upgrade flashboards and the e-mail engine too. 6. A new install of mid-tier messes up the CMDB visualization module -- make sure and reinstall that after a new mid-tier install. 7. Make sure an upgrade the LDAP plugins if you are using that. Notes -- If you know you have not made any customizations to the forms/workflow related to Email Engine, Flashboards, Assignment Engine, or the Approval Engine it should be an easy upgrade and go rather smoothly. -- Sometimes a server upgrade can mess up your settings in armonitor.conf. If you made a backup simply just restore the file and you should be good to go. -- Also if you are running any of the LDAP integrations make sure you make a backup of ar.conf so that you can restore it just in case the patch upgrade overwrites it (I don't think it does but best to be safe than sorry). -- By default remedy makes a backup of some of the directories where you installed remedy but it is not a bad idea to make a backup yourself so that you can easily recover if something goes wrong. Remedy's backup is a little bit more difficult to recover from since it only backs up a few directories like bin, conf etc and not the whole install you have of arserver. Other things to consider: Check to see if you need to patch ITSM to work with the newer patch of ARServer. Sometimes the SLA Engine, CMDB Modules, AIE, etc. work better when you upgrade their modules too (and prevent server outages). ITSM upgrades will overwrite custom workflow so make sure and back up any custom workflow before installing the upgrade so that you can put them back. As a general rule of thumb a "Server Patch"(i.e. patch 0 to patch7) goes rather smoothly but a "Server Upgrade" (7.0.x-7.5 for example) can be a nightmare depending on the compatibility of the ITSM modules, OS, and DB in addition to restoring customizations after the upgrade. Sean From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of MCarnevale Sent: Wednesday, October 07, 2009 10:40 AM To: arslist@ARSLIST.ORG Subject: BMC Server 7.1 - Have to upgrade to Patch 007 - What to backup? ** Hello, We currently are running ITSM suite and it is currently patched. I have my Server 7.1.00 with no patches installed onto it. I want to install patch 007 to my server but I am not aware of what will be changed or what should we backup or save prior? We have some customization and want to make sure it is not lost... I really need to plan this out properly... Thank you so much for any help Mike ________________________________ View this message in context: BMC Server 7.1 - Have to upgrade to Patch 007 - What to backup?<http://www.nabble.com/BMC-Server-7.1---Have-to-upgrade-to-Patch-007---What-to-backup--tp25787917p25787917.html> Sent from the ARS (Action Request System) mailing list archive<http://www.nabble.com/ARS-%28Action-Request-System%29-f716.html> at Nabble.com. _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
