Re: Test to see if another remote is syncing with the hub replica

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Since this post includes info on the time required for syncing, here is
something that I found interesting.

1) One of my users is in the building next to mine, about 50 feet away.
When I synchronize my remote backend with the server backend it takes
about 1 minute and 15 seconds (actually it's two backends which I've
never mentioned before just to keep things simple). However, it only
takes him 17 seconds to synchronize. This synchronization is for only
3 or 4 rows in one table that were changed.

This is a huge reduction in sync time which had me puzzled. Since I'm
a consultant, they don't give me a high powered machine. Mine has 256
MB of RAM and his 1GB. So at first I thought this might be the
difference, but it really doesn't make sense, since the network is
usually the main rate-limiting step.

Now I've discovered that his building was recently wired for the LAN
and they used fiber optic cable instead of traditional cable.

At any rate all of my users for the app are in his building, so as
Martha would say, that's a good thing, and therefore we will be using
direct synchronization at this location.


rdemyan@xxxxxxxxxxx wrote:
Thanks for the reply.

With this setup, you will never need to install additional software on
the server. You will need an independent hub computer at each LAN
location, which would be preferable to using a user's computer.

But don't you still need to install the Jet Synchronizer on the server.

Believe me I have every intention of using indirect synchronization if
they will allow it. However, for now I'm going to stick with direct
replication. I'm 100% convinced it will work at the site I'm usually
at (LAN connection). For the others, there are only two sites out of
four sites that I'm somewhat concerned about.

I plan to modify a utility program that I have. It will be used for
making replica backups, restoring replica backups (in case the server
backend becomes corrupted), etc. One thing that is important is that I
need to stop users from thinking they can just use the Windows file
system to make copies of the replicated backends. This might actually
be a bigger problem.

Since data doesn't get changed that often, I think this may work, but
will continue to pursue the indirect replication route (still
installing Jet Synchronizer on the server, I think, will be a major
problem).


jacksonmacd wrote:
On 20 Dec 2006 14:41:31 -0800, rdemyan@xxxxxxxxxxx wrote:


However, I did talk to IT and they may allow the Synchronizer after all
(since it is a Microsoft product and not a third-party product) at
least on user's PCs. I didn't mention that I might need it to run on
the server as well (I think they will be very resistant to this). With
these guys it is one baby step at a time. Ultimately, I'll probably
wind up coding both direct synchronization and indirect synchronization
into my app.


I've been following this thread for a while. David Fenton is giving
you sound advice -- do not consider using direct synchronization over
the WAN. If you do, it will come back to bite you eventually even if
it appears to be stable and reliable during your testing phase. Ignore
that advice at your own peril.

Here's an alternative if Terminal Server is also out of the question.

Set up your hub replica farm on an independent PC. The computer does
not need to be especially powerful. A reliable, but obsolete, desktop
computer will be sufficient. It will need to have Replication Manager;
MS Access is optional. No other software besides the O/S is required
although remote-control software is desirable.

Mount a replica on the server for the local users to access via the
LAN. Connect the hub replica computer to the server via the LAN.
Synchronize directly between the hub replica farm and the server-based
replica. The server-based replica remains *unmanaged* by the
synchronizer, but needs to be *scheduled* for synchronization. These
items can be specified separately in Replication Manager.

You will need to duplicate this setup for each of your LAN-based
installation. For mobile users, you will need to install the
Synchronizer so they can synchronize indirectly with their hub.
Alternatively, they can synchronize directly with the server-based
replica if they periodically connect to the LAN (not wirelessly).

With this setup, you will never need to install additional software on
the server. You will need an independent hub computer at each LAN
location, which would be preferable to using a user's computer.




--
jackmacMACdonald@xxxxxxxxxxxxxx
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security

.

Relevant Pages

  • Re: Test to see if another remote is syncing with the hub replica
    ... direct synchronization at this location. ... But don't you still need to install the Jet Synchronizer on the server. ... making replica backups, restoring replica backups (in case the server ...
    (microsoft.public.access.replication)
  • Re: Test to see if another remote is syncing with the hub replica
    ... But don't you still need to install the Jet Synchronizer on the server. ... making replica backups, restoring replica backups (in case the server ...
    (microsoft.public.access.replication)
  • Am I on the right track here?
    ... I like the sound of Scenario 4... ... server and you get an error, ... Don't use the Design Master as a user used replica, ... >synchronization would be automated. ...
    (microsoft.public.access.replication)
  • Re: Two or more users attempting to sync with the hub at the same time
    ... The connections to the server are excrutiatingly slow. ... app does a lot of complex calculations and analysis. ... their local replica with the server hub replica. ... I would *never* implement simultaneous synchronization with DIRECT ...
    (microsoft.public.access.replication)
  • Re: Test to see if another remote is syncing with the hub replica
    ... synchronization, then the MDB files at either end of the line are ... a slower connection is vulnerable to interruption ... But don't you still need to install the Jet Synchronizer on the server. ... making replica backups, restoring replica backups (in case the server ...
    (microsoft.public.access.replication)