It truly depends upon the complete requirements. I've used DSO for data replication (foundation) as well as ticketing replication quite successfully in "near time" synch.
As you might imagine, to circumvent a "DSO Overload" - I implemented a queuing mechanism because of what I term "ticket stabilization" immediately after submit. As you can think, a ticket gets Created, then many Updates occur to said ticket, and if simply implemented as a DSO Operation, that same ticket will get transferred multiple times, thus we build in a queue and waited about 5 minutes (configurable based upon ticket priority) prior to sending to the remote servers. We were keeping 3 global servers in synch... If you are using the remote server more as a reporting or DR type server - and NO ticket entry/update will be performed (unless DR is in effect) - then utilize other methods of sync - such as RRR / Database Replication (is this Oracle, SQL, etc?)... If this is a "Live / Live" setup as was mine - DSO certainly worked like a champ. HTH Robert Molenda On Fri, Mar 11, 2011 at 9:20 AM, Misi Mladoniczky <m...@rrr.se> wrote: > Hi, > > For archiving and copying data to a reporting server, I would recommend > RRR|Chive. > > It is fast, robust and foolproof, and will keep modify-dates and request > ids synchronized. > > It does not require any DSO-fields. > > When you need 2-way synchronization, I would go for DSO or database > replication of some kind. > > Best Regards - Misi, RRR AB, http://www.rrr.se > > Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10): > * RRR|License - Not enough Remedy licenses? Save money by optimizing. > * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. > Find these products, and many free tools and utilities, at http://rrr.se. > > > Vikram, > > I worked at a company that used DSO for exactly what you are discussing, > > used to archive things off of production to a reporting server, and make > > that reporting server 'real time'....it was a good solution for us at the > > time, but looking back, I wouldn't do it again. The DSO engine is NOT > > intended for data replication, as others have mentioned...it's really > > intended for follow the sun operations, as such its throughput is > > relatively > > slow for the task you are looking to do. We are embarking on a similar > > initiative at my current company and we are opting to go with db > > replication. Replication comes with its own set of baggage, but I > believe > > that baggage is manageable. > > > > -----Original Message----- > > From: Action Request System discussion list(ARSList) > > [mailto:arslist@ARSLIST.ORG] On Behalf Of vikram_k > > Sent: Friday, March 11, 2011 3:12 AM > > To: arslist@ARSLIST.ORG > > Subject: Using DSO to sync two AR Servers > > > > Hi listers, > > > > Greetings, > > > > I have a new challenge thrown at me.. now the performance of the system > is > > good enough (if you remember my tiring question about ARS performance and > > huge queries) now I have been asked to find a way to keep 2 application > > servers in sync at real time. And what I could think of is to introduce > > DSO > > to into the picture. So here it goes: > > > > 1) Is it best to use DSO to keep 2 Application servers in sync all real > > time. > > 2) Both the application servers are replicas of each other but > > geographically located. > > 3) The ARS application is completely customized with 350+ forms to be > > managed in sync. > > 4) Also DSO is to be used to archive data from one of the servers into > the > > other which will be used as just an read only reporting server. > > 5) Both the servers are ARS 5.0.1 :) > > > > So I would really appreciate if you can help me through this as well as > > you > > did in my previous endavour. > > > > My questions : > > > > 1) Is it reliabe to use DSO in this big context? > > 2) What all factors do I have to keep my eyes on while doing this? > > 3) What is the performance hit that if at all one can expect? > > 4) Any specific setting that can be implemented to keep the performance > > up? > > > > I guess this is a nice learing experience for someone like me and would > > like > > any help possible from you guys. > > > > > > Thanks in advance > > > > Regards, > > Vikram. > > -- > > View this message in context: > > > http://old.nabble.com/Using-DSO-to-sync-two-AR-Servers-tp31123715p31123715.h > > tml > > Sent from the ARS (Action Request System) mailing list archive at > > Nabble.com. > > > > > ____________________________________________________________________________ > > ___ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > > > > > _______________________________________________________________________________ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
