Two recent capabilities are intended to assist with these kind of situations.
1. The ITSM Preconfigured Suite Stack Installer. The Suite Stack Installer (SSI) enables a fresh install of the entire ITSM Suite to be installed in an hour or two. All of the applications and configurations are pre-loaded in a DB image provided by BMC – so the installer need only lay down the binaries and copy the DB image into an empty DB instance provided by you. Time has been reduced from up to 60 hours down to 1-2 hours for a fresh install. While the SSI cannot be used for upgrades, it is good for creating a staging, development or POC system. 2. Delta Data Migration. The ITSM Suite 7.6.04 includes utilities that enable you to migrate data from your production environment to a staging/development server until you are ready to switch over from development to production. Basically, you’ll create a parallel system in staging/development that will eventually become your production server. When your maintenance window arrives, you can bring down both systems, transfer the last bit of user data (which should be only a couple of hours or, at most days) and then bring up the staging server as your new production server. Downtime has been reduced to 4 hours or less using this methodology. -David J. Easter Manager of Product Management, Remedy Platform BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Patrick Zandi Sent: Saturday, January 29, 2011 05:27 AM To: [email protected] Subject: Re: Long running ITSM 7.6 upgrade ** 7.6.04 might (don't know yet) be a faster method. But UT is Not supported Sent from my iPhone On Jan 29, 2011, at 8:14 AM, "Gard, Richard J" <[email protected]<mailto:[email protected]>> wrote: ** Our plan is to install 7.6.03 on bare metal (new hardware) and migrate our SRM, RKM and CHM apps to it. No-one uses the new system until migration is complete and tested. The current Prod system will then become UAT, and our UAT systems will become part of DEV. We don't do upgrades often, so this approach seems to work best. We support 3000+ demanding global users who operate 24/7. We can't afford down time of more than 4-5 hours on a Friday night. The switch is more of a DNS repoint and test. From: sphilben [mailto:[email protected]] Sent: Friday, January 28, 2011 02:40 PM To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Subject: Long running ITSM 7.6 upgrade All: We are in the process of working out our upgrade path from ARS 7.1/ITSM 7.0.03 to ARS 7.6/ITSM 7.6. The upgrade of ARS is pretty straightforward and relatively quick. The ITSM pieces, on the other hand, take forever. The upgrade path looks like this: SRM 2.2 p4 CMDB 7.5 p5 SRM 7.6 p1 CMDB 7.6 p2 ITSM 7.6 p1 SLM 7.6 SLM 7.6 p1 I am currently working on ITSM 7.6 on our DEV server. Should it really take 10+ hours? How am I supposed to get this done during our maintenance window? Has anyone else gone through this mess and survived? Does anyone have a strategy on how to get this done in less than 24 hours (or whatever it ends up taking)? We have failover servers that we could try and use but I don't see how we can do it there early (like we are going to do during the ARS upgrade). Not sure how I can go to the powers that be and tell them they will be down for a whole day in order to upgrade some software. Thanks. _attend WWRUG11 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_
