Thanks Doug, That is along the lines I was thinking.. In this case it might be ok.. The thought here was more of a DNS - CNAME Remedy.Sub.Domain.com xxx.yyy.zzz.000 After server crashes (01 Server Group) DNS - CNAME Remedy.Sub.Domain.com NEW.IP.For.ARS .. a hot HA, just change the DNS record, but it may occasionally submit a record here or there..
This way you have 2 Application servers, setup on the same DB, the DB is oracle Dataguard-broker back to the ServerGroup #2 (long distance) for DR capability. Then if the first site turns into a Crater or gets removed from the earth, you would then shutdown #2, change the oracle db connection and turn it back on. Duel purpose.. That is what the original thought was. but if it slows it that bad, it might be not be viable. Especially if they both have to come up together, one awaiting the slow server.. On Mon, Apr 26, 2010 at 3:51 PM, Mueller, Doug <[email protected]> wrote: > ** > Patrick, > > Technically, this will work assuming all the definitions are set up. > > However, it is not a good practice and it is not recommended by BMC. > > The highest volume connection in the system is the connection between the > AR System server and the > database. We have found that ANYTHING and that means ANYTHING that is > between the AR System server > and the database has a dramatic affect on overall performance. Things > work, but just much slower. > > If there is a firewall or a router or a WAN or anything at all other than a > wire with backplane speeds, the > overall performance and throughput of the system suffers. As was noted by > another poster, you may see > things like startup of the system go from 2 minutes to 40 minutes. You may > find that retrieval of lists of 10s > and especially 100s of items take 5, 10, or even more times longer (not > percent, but times). > > The question is why you would set up a configuration like this? Why not > both servers located close to the > database and then go remote from there? This puts a significantly lower > bandwidth of traffic on the network > (order of magnitude ore more less) to go remote from AR System server to > client than from AR System server > to database. > > It is also more flexible because the AR System server to client connection > has retries and auto reconnect > and is connectionless so things going up and down are immaterial and > invisible while the AR System server > to database is connection oriented, is stateful, and has minimal > auto-retry, auto-reconnect options > (essentially, the AR System server goes down with the loss of the > connection and then starts up and tries to > connect to the DB on startup and if the startup went to 30 minutes or more, > that means a line hiccup > generates an outage. > > Some things to think about. > > Doug Mueller > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *patrick zandi > *Sent:* Friday, April 23, 2010 2:44 PM > *To:* [email protected] > *Subject:* Re: Server Group -- not co located > > ** > >> Any issue with running a server group with >> Server 01 is in Ohio - Database here >> Server 02 is in Nebraska Connected to Database in Ohio >> >> OC-3 minimum connection >> >> Anyone see any issues with this ? >> >> P.S I know Nebraska would win the football game.. that is a no brainer. >> -- >> Patrick Zandi >> > > > > -- > Patrick Zandi > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > -- Patrick Zandi _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

