If you have made any customizations to the User or Group form (never recommended but sometimes necessary) they will be overwritten. Any AR System form will probably be updated (views overwritten at a minimum) as well, so if you customized the mail form or something else, you will need to back up the modifications. If you have modified any portion of the password management workflow, as we had, it will be overwritten as well.
When you upgrade the email engine, be sure to go ahead and configure the mailboxes even though they already are, then go back and delete the new configuration records that creates. Otherwise the password information won't be re-written to the EmailDaemon.properties file correctly and the service may not work (after which you get to uninstall it, and do a new install). In my experience, the 7.0/7.1 patch installers will frequently trash your mid-tier and aremail installations rather than upgrade them properly, so that frequently they must be uninstalled and reinstalled with the newer patch. In a similar 7.x observation, you _do_ want to use the installers instead of file replacement, especially for the AR Server itself. Unlike on ARS 5.1.2 (our last production platform before 7.1.00.002), where by file replacement patching worked fine, the 7.x servers will often have problems starting the java plugins after a by file patch, and you will have to run the installer to fix it anyway. The safest thing to do is upgrade your development environment, then use Migrator to compare it against production to sense the changes. Then migrate the customizations back from production to development and _document_ what you had to move. Now you are ready to upgrade production, after which you will migrate exactly the same customizations back from development according to your checklist. ARS isn't nearly as bad as ITSM about overwriting things, but this was the process I used recently to successfully patch ITSM 7.0.03 from 007 to 009. Your mileage may vary, but this is my experience with 7.x over the last three years, all on Windows 2K3 64 or 32 bit servers. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of MCarnevale Sent: Wednesday, October 07, 2009 9:40 AM To: [email protected] 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: [email protected] ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
