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 < frederick.w.gro...@xo.com> 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: > arslist@ARSLIST.ORG] On Behalf Of Su Kaur > Sent: Friday, January 15, 2016 10:23 AM > To: arslist@ARSLIST.ORG > 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: > arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W > Sent: Thursday, January 14, 2016 10:04 PM > To: arslist@ARSLIST.ORG > 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: > arslist@ARSLIST.ORG] On Behalf Of Kaur > Sent: Thursday, January 14, 2016 9:51 PM > To: arslist@ARSLIST.ORG > 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" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
