I've had success with vcs on solaris working around these types of issues. Axton Grams
On Fri, Jan 16, 2009 at 9:57 PM, John <john.sundb...@kineticdata.com> wrote: > ** > Back when I was managing a Remedy system - we had this issue and lots of > others. > (all were solvable) > > The best thing we did was "switch systems monthly" -- meaning every month > we would switch the "prod box" -- from boxa to boxb. > > Eventually we had it down quite well. It uncovered lots of things that we > would have never figured out - unless it was real. > > > The #1 hardest thing to solve was this: > > (Updating DNS records -- and the built in caches that all the clients had). > > Meaning -- we would migrate from boxa to boxb -- which was something like > 192.168.1.50 -- to 192.168.2.20 > > All the clients knew the machine as boxz -- and the DNS would alias that to > boxa -- and then clients would have boxz IP address as 192.168.1.50. > > When we would switch from boxa to boxb -- we could update the DNS quickly > -- but the clients all held the old address for (an hour ????) -- I don't > remember (12 years ago now). > > > At the time -- you did not have the option of saying this IP address was > not cacheable (or had a small cache) -- so we had to create a new DNS domain > and register boxa,boxb,boxz all in the new domain. Then that domain would > have something like a 15 second cache window. > > (blah blah blah) > > > Anyways -- that is the type of thing you have a hard time predicting. (And > many other issues too) > > > If I was actually adminning (made that word up) -- I would feel much more > comfortable if I switched every once in awhile. > > > > > -John > > -- > John David Sundberg > 235 East 6th Street, Suite 400B > St. Paul, MN 55101 > (651) 556-0930-work > (651) 247-6766-cell > (651) 695-8577-fax > john.sundb...@kineticdata.com > > On Jan 14, 2009, at 3:17 PM, Pierson, Shawn wrote: > > **The questions about upgrading to ARS 7.1 lately have gotten me thinking > about something. > > For our disaster recovery solution, we have a failover server sitting in > another city, with a different server name, etc. We use log shipping in SQL > Server 2005 to keep the two databases synchronized. In the event of an > emergency, we have the DBAs mark the normal production database as read > only, and we open up the disaster recover database, and we proceed from > there. > > Since ARS 7.1 stores the license keys in the database, how would I prevent > this from being overwritten? How would I keep my DR copies of the licenses > on the server if the database is overwritten constantly? Or is this not an > issue in 7.1 since it sounds like you can temporarily create licenses on the > fly anyway? > > Thanks, > > *Shawn Pierson* > Remedy Developer | Southern Union > 5444 Westheimer Rd. Houston, TX 77056 | 713.989.7226 > > > > Private and confidential as detailed > here<http://www.sug.com/disclaimers/default.htm#Mail>. > If you cannot access hyperlink, please e-mail sender. __Platinum Sponsor: > RMI Solutions ARSlist: "Where the Answers Are" html___ > > __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
