How to create backups/failsafes for Replication Manager/A97?

andersonm82

New member
Local time
Today, 22:25
Joined
Oct 26, 2006
Messages
7
I have tentatively gotten an indirectly synchronised database system to work on a testing basis, in the following way:

1. Design Master - resides on network.
2. Replica Master - replica of master, resides on network
3. Local replica on the windows desktop of my laptop (as one of few folders with write authority). These three are managed by a synchroniser running on my laptop.
4. Other people (3-6) also have synchronisers running - managing the Replica Master, and a local copy on their desktop only.

This appears to work. It was done as we did not have access to get a synchroniser process running on a server, just folder access (I am amazed IT accepted this without oversight, anyway..). I would be happy to describe the procedure.


However, does anyone have any advice on potential things that could go wrong and how to avoid them? What problems could crop up? I don't believe database size would be one of them. How about backups? I know that the network is backed up daily and can be restored to any day - but would this method of backup create any problems if restoring? How rare are collisions/conflicts?

Also, is there any limitations to using the Compact utility in Access on either the replica master on the design master? Would this cause changes to get lost?

Would be grateful for advice.

Edit: Addition, just as I was submitting this, my synchroniser appears to have gone into a loop... From the log file:


Time = 2007-01-22 01:23:55 PM
Log Type = Close exchange
Replica = \\afsukhofs02\N_Dept\[Folder names]\Replica master.mdb
Exchange ID = {D4C646CE-140A-4DE0-B164-FE924A44C7A3}
Result = Failure

Time = 2007-01-22 01:23:56 PM
Log Type = Cancel exchange
Replica = \\afsukhofs02\N_Dept\[Folder names]\Replica master.mdb
Exchange ID = {D4C646CE-140A-4DE0-B164-FE924A44C7A3}
Reason = More than one synchronizer is managing the replica


This looks to be a problem... Is it caused by having multiple synchronisers managing the same replica? Does it work to set them to manage the local one only? Advice GREATLY appreciated. :P
 
Last edited:
I don't know about the problem that you added at the end, but I'm concerned about whether or notyou have your master replica (i.e., not the DM) managed by more than one synchronizer. That's a potential problem, seems to me, as the synchronizers won't know anything about each other. There should be one designated synchronizer for managing the master replica only.

In regard to compacting, a managed replica can't be compacted until the synchronizer is shut down, because the synchronizer keeps every managed replica open as long as the synchronizer is running.

Also, I try not to do my synchs with my production hub replica. I'd tend to have a master replica that is edited by LAN-connected users, and a hub replica that is used for synchronizing with the remote users. That would need to be synched on a schedule or on demand with your master replica.

--
David W. Fenton
David Fenton Associates
http://dfenton.com/DFA/
 

Users who are viewing this thread

Back
Top Bottom