such as myself :) On Fri, Jan 15, 2016 at 2:10 PM, Jason Miller <[email protected]> wrote:
> ** > LOL! That is silly, it is a platform feature not ITSM. Putting it under > ITSM will likely make people think you can upgrade ITSM with zero downtime. > And there are the platform only users that would never go looking in ITSM > docs. > > Jason > > On Fri, Jan 15, 2016 at 11:14 AM John Johnson <[email protected]> > wrote: > >> ** >> Doug and all, >> >> They moved the install docs into its own section called Remedy ITSM >> Deployment >> >> Specific section on zero downtime upgrade - >> https://docs.bmc.com/docs/display/public/brid91/Upgrading+platform+components+with+zero+downtime >> Upgrade section - >> https://docs.bmc.com/docs/display/public/brid91/Upgrading >> Top level - https://docs.bmc.com/docs/display/public/brid91/Home >> >> On Fri, Jan 15, 2016 at 1:41 PM Mueller, Doug <[email protected]> >> wrote: >> >>> ** >>> >>> LJ, >>> >>> >>> >>> You are not misquoting (one minor qualification needed), but you are >>> correct. >>> >>> >>> >>> With the 9.0 sp1 release, we have fully tested and documented a process >>> to allow zero down time upgrades of the platform (not out of the box >>> application upgrades, but the AR System/CMDB/mid-tier). >>> >>> >>> >>> From before 9.0, there are a couple of configuration things you do. >>> After 9.0, most of those have been removed to further simplify the process. >>> >>> >>> >>> This has been fully tested upgrading from 7.6.04, 8.0, 8,1, and 9.0 >>> (any patch/servicepack/hotfix level). >>> >>> >>> >>> All of this is supposed to be documented on the on line documentation – >>> although I have to admit that with 2 minutes of looking I did not find it >>> and I should have been able to so it is not as up front as it should be…. >>> A call to support asking for the documentation should get it for you. >>> >>> >>> >>> >>> >>> Now, you mention 7.6 which is before versions we have tested with… So, >>> I cannot guarantee that there would be no issues if you tried to follow the >>> zero down time directions from that version. It won’t break anything, but >>> there is the possibility that servers would come down so you don’t get zero >>> down time. You could always try it in a test environment and see what >>> happens. >>> >>> >>> >>> >>> >>> The ability to fully upgrade the platform – mid-tier, AR System, CMDB – >>> without down-time is a significant advance. It allows true 24x7 operation >>> even to change out the processes themselves. As of the next release of >>> SmartIT and MyIT, those components will also have a zero down time upgrade >>> capability so that all aspects of the componentry of the platform can be >>> upgraded without end user outage. >>> >>> >>> >>> >>> >>> But, in general, if you don’t have a problem with a 30 to 60 minute >>> outage, you can simply upgrade from 7.6 to 9.0 in place and it should just >>> work. (yes, I see another thread where 7.1 to 8.1.2 is having some trouble >>> for a customer, and that should work too, but that is a release that is 4 >>> years or so older than 7.6). >>> >>> >>> >>> Doug Mueller >>> >>> >>> >>> *From:* Action Request System discussion list(ARSList) [mailto: >>> [email protected]] *On Behalf Of *LJ LongWing >>> *Sent:* Friday, January 15, 2016 10:09 AM >>> >>> >>> *To:* [email protected] >>> *Subject:* Re: Upgrade from 7.6 to 9 >>> >>> >>> >>> ** >>> >>> Fred, >>> >>> I'm probably going to mis-quote Doug (as seems to happen often), but at >>> Engage last year, Doug said it's possible to do upgrades without 'down >>> time' in server group environments, and I think he said (here is where the >>> mis-quote could happen) it was even possible from 7.6 to the latest >>> versions. You simply take the server being upgrade out of the load >>> balance, upgrade it, when the upgrade is done, you put it back in the load >>> balance, then do the same for the next server, etc.... >>> >>> >>> >>> According to my remembrance of the session, this entire process is >>> documented and available to the masses in the docs.bmc.com stuff :) >>> >>> >>> >>> On Fri, Jan 15, 2016 at 10:28 AM, Grooms, Frederick W < >>> [email protected]> wrote: >>> >>> If you are upgrading a server "inplace" then there is no copy to new >>> prod as there is no new prod (same hardware, same database, just updating >>> BMC forms and workflow). There will be downtime for the users while the >>> upgrade is running (On our Linux/Oracle servers from 7.6 to 8.1.2 it was >>> about 30 minutes. We are also pure custom, base development mode, no >>> additional BMC products) >>> >>> Fred >>> >>> -----Original Message----- >>> From: Action Request System discussion list(ARSList) [mailto: >>> [email protected]] On Behalf Of Su Kaur >>> Sent: Friday, January 15, 2016 10:23 AM >>> To: [email protected] >>> Subject: Re: Upgrade from 7.6 to 9 >>> >>> No, we are not using overlays. Everything is in base development mode. >>> Upgrade would be on Windows system. >>> How about the data/tickets that are modified during the upgrade? How can >>> we copy that change to new prod? >>> >>> Thanks! >>> Kaur >>> >>> -----Original Message----- >>> From: Action Request System discussion list(ARSList) [mailto: >>> [email protected]] On Behalf Of Grooms, Frederick W >>> Sent: Thursday, January 14, 2016 10:04 PM >>> To: [email protected] >>> Subject: Re: Upgrade from 7.6 to 9 >>> >>> Part of it depends on your hardware and OS. If you are pure custom, >>> are you using Overlays? >>> >>> How many environments do you have? Normally a code freeze should be >>> from the first environment upgrade until you finish the last, although if >>> you have multiple test then as long as you keep one of them the same as >>> production (and do it after production) then the freeze can be shorter. >>> >>> Fred >>> >>> -----Original Message----- >>> From: Action Request System discussion list(ARSList) [mailto: >>> [email protected]] On Behalf Of Kaur >>> Sent: Thursday, January 14, 2016 9:51 PM >>> To: [email protected] >>> Subject: Upgrade from 7.6 to 9 >>> >>> Hello All, >>> >>> We are planning to upgrade 7.6 to 9. What is the best way to do it for a >>> highly customized environment - Not using any OOTB modules? Inplace >>> upgrade? Downtime should be minimum. >>> Should we do a code freeze and how long would it be? >>> >>> Any insights would be helpful. >>> >>> Thanks! >>> Kaur >>> >>> >>> >>> >>> >>> _______________________________________________________________________________ >>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >>> "Where the Answers Are, and have been for 20 years" >>> >>> >>> >>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
