So, if you using Log shipping, how you failover ARS-servers in case of primary DB server fail? Manually changing Server Name in ar.cfg or there is a more capable way?
Kaiser Norm E CIV USAF 96 CS/SCCE wrote: > > This is the root challenge of a SQL mirror in a Remedy environment. > > There are two fundamental high availability/failover options in Microsoft > SQL: Mirroring and clustering. With a mirror, two or more instances of > Microsoft SQL server operate in tandem to share data. The issue with > this, however, is that both instances of SQL have their own respective > instance names. Thus, to applications, it is clear that these are two > different SQL servers. This is not much of a problem with custom built > apps because, as you indicate, in a custom built app you control the > connection string. > > In Remedy, however, because the code is compiled and closed-source, you > have no access to the connection string. > > So in a mirrored environment, everything hums along seemingly fine until > the dreaded day that your primary database fails. At that point, your > Remedy server does not know to "talk" to the failover because, to Remedy, > it doesn't even exist. > > With clustering, on the other hand, two or more machines are combined into > one virtual instance of SQL. Thus you can configure two separate servers > into a cluster and those two separate machines appear on the network and > to applications as ONE database server. Thus, one server can fail but the > cluster will just continue humming along and your application is none the > wiser. > > Clustering, to me, seems to be the best option for Remedy environments; > however, from my understanding it still requires special, expensive > hardware (i.e., dedicated fiber channel) to connect the disk drives. > > In my current environment we employ transaction log shipping, but that's a > warm failover, not hot. > > I would be very interested in reading the comments of other listers on > this subject and how they tackle the issue. > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of DenisBG > Sent: Tuesday, August 19, 2008 8:21 AM > To: arslist@ARSLIST.ORG > Subject: ARS with SQL 2005 Database Mirroring setup > > Good day everyone! > > Have somebody successfully setup ARS to work with mirrored SQL2005 DB and > automatically failover? > Ноw I need to configure ARS to know failover partner server name(mirror > DB-server)? MS recommend to use client connection string like > "Server=PRIMARY SERVER; Failover Partner=MIRROR SERVER; Database=DATABASE > mNAME; Network=NETWORK NAME", but WHERE I can insert this string in ARS > (version 7.1)? > > Will be grateful for any help. > -- > View this message in context: > http://www.nabble.com/ARS-with-SQL-2005-Database-Mirroring-setup-tp19048755p19048755.html > Sent from the ARS (Action Request System) mailing list archive at > Nabble.com. > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > > -- View this message in context: http://www.nabble.com/ARS-with-SQL-2005-Database-Mirroring-setup-tp19048755p19051981.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
