Re: Indirect synchronization setup with no synchronizers on servers
- From: "David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx>
- Date: Sat, 23 Dec 2006 15:19:27 -0600
rdemyan@xxxxxxxxxxx wrote in
news:1166833177.459060.173600@xxxxxxxxxxxxxxxxxxxxxxxxxxx:
First off let me say that you have been very generous with your
time and detailed explanations in all my posts and it is very much
appreciated. I know you have in some cases said the same thing
over and over again and that can be frustrating.
I put the time in in part because I want to create a record for
other replication users that can help them work through all the
problems. I've had about ten years to learn all of this stuff. You
are needing to learn it in a few weeks. I definitely wish someone
had told *me* about the downside of direct replication across a
non-LAN connection way back when. It would have saved me a lot of
headaches and one of my clients thousands of dollars.
Part of the issue is terminology as you note, my lack of knowledge
on this issue, and I think the other part is the restrictions I'm
forced to operate under. For example, I may be able to get the
jet synchronizer installed on "workstations" but I doubt they will
allow Replica Manager to be installed at all. TSI applications
are out of the question under all scenarios (third-party).
JRO doesn't supply all the functionality that is found in the TSI
Synchronizer.
But you *don't* need to install Replication Manager. If you have it,
great, but all that needs to be installed is the synchronizer. I've
pointed you to my instructions for how to do this without even
having ReplMan at all.
If I get the opportunity to implement indirect then I'm not going
to trust any LAN, except the LAN where the file server is that
stores my application files. That particular LAN is highly
reliable and very fast. But all others will assume indirect
replication. You're probably thinking that this is strange given
my earlier stance on direct synchronization if indirect is not
available. I don't mind putting the coding work in if indirect is
available to me.
I see that as way too much trouble, and have no idea why you
wouldn't trust any of the LANs. Are they wireless or something?
The topology I suggested was because I was trying to minimize the
installation requirements to get by the IT department's
restrictions. My scenario would require the synchronizer only on the
servers at the hub of each LAN group.
The other issue is that indirect replication introduces latency
because you can't synch indirect with your production LAN replica
(because the latter has to be shared and the former must *not* be
shared). I'd prefer to minimize latency as much as possible, because
that increases conflicts.
And you're buying yourself headaches in supporting all those
indirect users. With servers, you'd likely be able to get remote
access to them and be able to administer and troubleshoot the
synchronizer that way. With a bunch of workstations, it's less
likely for you to get this permission.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.
- Follow-Ups:
- References:
- Indirect synchronization setup with no synchronizers on servers
- From: rdemyan
- Re: Indirect synchronization setup with no synchronizers on servers
- From: David W. Fenton
- Re: Indirect synchronization setup with no synchronizers on servers
- From: rdemyan
- Indirect synchronization setup with no synchronizers on servers
- Prev by Date: Re: Is there a way to tell if two replicas need to be synced without starting the sync process
- Next by Date: Re: Indirect synchronization setup with no synchronizers on servers
- Previous by thread: Re: Indirect synchronization setup with no synchronizers on servers
- Next by thread: Re: Indirect synchronization setup with no synchronizers on servers
- Index(es):
Relevant Pages
|