John Skolits
askolits at ot.com
Mon Jul 14 11:52:21 CDT 2003
I will have one replica here (my officer) and the other 2 on remote servers. All servers connected to each other via VPN. Can't do direct because I've read it's a bad idea to do that on WAN. I think I'm slowly figuring it out except, I've read where: "To prevent direct synchronization from occurring, make sure the replica is not stored in a shared folder; " I want to have the replicas on 3 servers all with synchronizers running with indirect Synchs. Then use those replicas as backends to various frontend applications. The FEs will be linked to the replica in their perspective local server. But, in order to link I have to share the database folders. The white paper indicated, if I shared the folder, then a direct sync would occur (implied: Even over a VPN). So it looks like I can't have a FE/BE design on replicas that run with indirect synching. What do you think? John -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Arthur Fuller Sent: Monday, July 14, 2003 11:47 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Replication - how can I tell if indirect occurring I'm not sure why you would want to set up indirect replication, since direct works. But you can change this by running Replication Manager and on the Tools menu select Configure Replication Manager. Follow the steps. Next question: why are you running two synchronizers? Only one is required in your scenario. It doesn't matter which machine it's on. Third question: where is your design master? Normally, the way you set it all up is this: 1. Design master on your machine. 2. Synchronizer on any server visible to all your replicas. 3. RM set for direct replication, but not including your design master. (i.e. the design master is an unmanaged replica.) 4. Set the synchronization schedule to whatever interval suits your requirements. 5. Make any changes you want on the design master, including adding or changing tables, etc. 6. After testing new code and features, etc. manually synchronize the design master with any of the replicas. The synchronizer will propagate the changes to all the replicas on the next interval. Hth, Arthur -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Skolits Sent: July 14, 2003 9:28 AM To: accessd at databaseadvisors.com Subject: [AccessD] Replication - how can I tell if indirect occurring I've been struggling with this replication stuff for quite a while. I think I set everything up for indirect replication but it seems it's doing a direct but I'm not sure. The synchronizer.log file tell me tons of stuff, but I see "direct" in various places and also "FS". So I'm assuming a direct connection. Yet, I want indirect. I have a network with 2 PC's each running a Synchronizer. Each PC is managing a separate replica in the same replica set. I made sure each synchronizer has been set up for indirect synchronization. The replicas are 'not' in shared folders. I see both synchronizers in the Replication Manager screen, connected by a solid line. Does the solid line mean direct? For those who are also familiar with SQLServer, do the synchronizers broadcast their presence on the network like SQLServer? Is that how replication manager is aware of the other synchronizers? Thanks, John Skolits _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com