Re: Question about potential for corruption when doing direct sync over a WAN



user@xxxxxxxxxxxxxx wrote in
news:eb#vlY9JIHA.4476@xxxxxxxxxxxxxxxxxxxx:

David W. Fenton wrote:
user@xxxxxxxxxxxxxx wrote in
news:uSN$Ay7JIHA.3516@xxxxxxxxxxxxxxxxxxxx:

I have read about not doing a direct sync over a wan because of
the potential for corruption. As I understand it, the replica
that is not local to the requesting replica is copied across the
link and updates are made in both direction. I also understand
that if the link breaks or disconnects, that corruption can
occur.

My question is whether the potential for corruption is on both
replicas or only the one at the far end, which had to send data
in blocks across the link?

The potential for corruption is in the remote replica, though I
guess it could happen in the local one, too.

Direct synchs should never be done over a non-wired LAN
connection of anything less than 10Mbps bandwidth.

My interest is in how it could happen to the local one.

Well, corruption can happen on a local LAN in replicated and
non-replicated apps, and doesn't necessarily happen because of a
dropped connection. All sorts of things can cause the problem, such
as bad Jet versions, or non-optimal versions of the MS Access
program file.

why I ask is as part of my trying to figure out some cases - 3 -
of database corruption on laptop based replicas. The replica on
the laptop which initiates the sync to the LAN - is the one where
the corruption occurs. Never on the LAN!

Do you have memo fields stored in your replicated tables? Are the
users allowed to synch while they have forms open?

As I have been considering problems of networking hardware or LAN
connectivity as a potential cause for the corruption, that is why
I have asked.

It doesn't sound like that would be the case, given that it's the
local replica being corrupted. I assume the synch is being initiated
*from* the laptop?

I would sure like to know from any MVP who might have access to
some of the Microsoft restricted newsgroup items and/or access to
some of the Microsoft Access team, if you can get corruption at
the replica initiating the sync in the case of a failed sync due
to connectivity.

Chances are, nobody who is a current MVP knows these things, as
nobody does Jet Replication any longer.

My thought is if I could rule this out then I could pursue other
possibilities such as the user shutting down the laptop with the
database still open.

A chief cause of replication corruption is running a synch while a
memo field is in a state of being edited.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.



Relevant Pages

  • Re: UNKNOWN REASON (-1017)
    ... replica before it lost replicability, however, to get anything you ... > laptop so I was spared manual data merging. ... > source of the corruption, my client could only tell me that he was ...
    (microsoft.public.access.replication)
  • Re: UNKNOWN REASON (-1017)
    ... > replica before it lost replicability, however, to get anything you ... >> source of the corruption, my client could only tell me that he was ... as possible after he reconnects to the network, and also so that his local ...
    (microsoft.public.access.replication)
  • Re: Question about potential for corruption when doing direct sync over a WAN
    ... As I understand it, the replica ... that if the link breaks or disconnects, that corruption can ... of database corruption on laptop based replicas. ... I have a sync button on the main menu. ...
    (microsoft.public.access.replication)
  • Re: A linked concept for synchronization
    ... >> shared back end when users are connected to the network. ... No. I'm suggesting that when the laptop users are connected to the ... shared replica on the server. ... bandwidth WAN connection. ...
    (microsoft.public.access.replication)
  • Re: Difficulty with Access partial replication - help please
    ... again solved the corruption problem, and now all of the selected ... >> all three clinics. ... >> The parital replication wizard works if I specify particular patients ... >> coming through in the replica, but certainly not all of them. ...
    (microsoft.public.access.replication)

Loading