5/12/2025 10:34:31 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss SalesLogix synchronization and remote database management. View the code of conduct for posting guidelines.
|
|
|
|
Run Multiple Sync Servers for Remote Office
Posted: 10 Jun 08 5:31 PM
|
Regarding a client's site:
Right now we have a Main Office running Sync Server on their own database.
There is also a Remote Office (several users at this location) with its own database, running Sync Client on a user logged-in session.
We are experiencing never-ending issues with syncing in both directions, and it is resulting in chaos any time the sync client is turned off or lost. We have tried all the standard work-arounds (manually syncing multiple times, un-releasing and re-releasing new plug-ins, with a sync done inbetween, copying TEF's from the Archives to Outfiles, etc.)
Obviously this is unacceptable to our customers, and it is definitely unacceptable to us because of the baby-sitting required.
My question is this: Can I run a Sync Server for my Remote Office instead of the Sync Client? It seems to me the sync client is just that: a client process, intended for offline end-users to update their data. Not to keep two distributed offices up-to-date with one another.
My ideal environment, and the only one I can think of that makes any sense, is to have two sync servers on either end, running automatically with all the infrastructure, conflict resolution, and built-in processes that accompany them, set-up and put in place to solve this issue.
Does anyone have some insight on how to solve this nagging problem once and for all? The client's employees are worried about their data loss, and I am personally worried about the ability to issue further customizations.
Thanks,
Jason
Unison
|
|
|
|
Re: Run Multiple Sync Servers for Remote Office
Posted: 11 Jun 08 6:50 AM
|
General notes about sync:
A - There is no sync as a service for remotes.. neither remote office or individual - there are some "tricks" in getting the remote office sync to automatically run. Mike Spragg, me, and others have set this up for our customers. However, it's not a "cookie cutter" deal.
B - The Sync "Server" and the Sync "Client" are "mirrors" of each other - you cannot swap pieces around like you are suggesting.
C - Sync works.. 99.9% of the problems with sync are related to install/setup issues.
D - Don't use "LAN" sync.. it's not secure and it's where the vast majority of problems happen. Use ftp sync or http(s) sync.
E - If there are multiple sync servers, Remote Offices MUST be assigned to the primary/first sync server.
F - Each RO should have it's own STP and set of directories (IN/OUT/FAILED). You should break down individual remotes to no more than 5 users per STP as well.
I could go on about sync for a page or 20...
Sync setup and monitoring is a very maual and labor intensive activity. We recognzed this years ago and developed tools/processes to ease this.. and no .. don't count on Sage stepping in to provide this..
Working with the TaskCentre folks we developed "SyncLogix" (tradmarked) - a comprehensive set of tasks - to automate a lot of this. Contact me off-line if you have an interest.
--
RJLedger - rjlSystems
"...Customer First..." |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|