Joe, I agree.
Also - it is like this ... the closer you get to no downtime - the more expensive the migration. (roughly) 1 week of downtime -- migration costs $15,000 1 weekend of downtime -- migration costs $50,000 1 day of downtime -- migration costs $100,000 1 hour of downtime -- migration costs $200,000 1 minute of downtime -- migration costs $300,000 I know of very few (probably none) -- that when presented with the costs of an upgrade like this - that they would choose the 1 minute of downtime. (Most would fall in the weekend space) Also - I would imagine... If they presented to their company that we could either 1) Upgrade over a weekend (60 hrs) - at a cost of $50,000 or 2) Upgrade and only be down (1 hrs) - at a cost of $200,000 99% would go for the #1 option -- and complain about that cost too. Hey - the formula might just be: (Roughly) Cost = $10,000 / % of the day down. -John On Wed, Mar 19, 2014 at 12:06 AM, Joe D'Souza <[email protected]> wrote: > Within certain limits though. > > I would not go that far to claim to the customer/management that there will > be absolutely no down time during code migration. > > There will be. > > By taking servers on and off a server group, to upgrade core system > versions, yes that can be done with 'minimal' down time. But the migration > and code upgrade, takes as much down time as the migration of the code > itself takes. > > Even if you stand up a completely new parallel system, and then decide a > switch by mirroring a database, there still will be that minimal time > required to port the delta data. > > Personally I think it is not possible to completely eliminate downtime if > your system is significantly large. Its like approaching infinity in > mathematics - you can get close, but you can never get there. You just got > to be content you got close enough.. > > Cheers > > Joe > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Zandi > Sent: Tuesday, March 18, 2014 6:49 AM > To: [email protected] > Subject: Re: BMC Remedy and Flash > > 24/7 is already there... It is called server groups, if you implement this > would can take a server down and the others will takeover while it is being > patched. You will need a load balancer as well. This also allows for > larger system use as well > My 2 cents > > Sent from my iPhone > > > On Mar 17, 2014, at 3:12 PM, James Smith <[email protected]> > wrote: > > > > Nice info Doug, thanks for sharing. Want to add 2 cents if its considered > then its of great use. > > > > Currently we have windows based tools for development activities and data > migration like Developer studio and Import tool. Will it be feasible to > make > then available over web? > > > > One more thing, how can we make remedy to be available 24*7 during > upgrades as well - zero downtime upgrades. This will help the product to > compete in the market. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > -- *John Sundberg* Kinetic Data, Inc. "Your Business. Your Process." 651-556-0930 I [email protected] www.kineticdata.com I community.kineticdata.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
