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!
|
| |
|
Re: Best Practise of Sync Maintenance 
Posted: 12 Apr 06 11:07 AM
|
fiogf49gjkf0d Kener,
I'm not sure I understand what the problem is that you are having. You certainly shouldn't need to be recutting databases every two weeks. Just keep the users synchronizing and all should be fine.
What problem are you experiencing related to synchronization? |
|
|
|
Re: Best Practise of Sync Maintenance
Posted: 12 Apr 06 7:48 PM
|
fiogf49gjkf0d Ryan,
Thanks for your reply!
Customer often tells me his/her data is losing, he/her can't see the latest update data, he/her sync is down. Sync client often prompt them "Older than your database of newer than your database."
I want to know SLX Expert's Best practice of Sync maintenance!
How to set the sync server best cycle? How to set the sync client's cycle?
I know how to monitor the sync server, I understand how to find the sync issues, but I'm so tired!!
Could you tell of your maintenance experience?
|
|
|
|
Re: Best Practise of Sync Maintenance
Posted: 18 Apr 06 3:51 AM
|
fiogf49gjkf0d For a start, if you are cutting remoe databases every two weeks (which you really shouldn't need to do) you will get this message quite often "Older than your database of newer than your database." It's not an error as such. All it is stating is that the remote client is receiving changes from the previous cut of the database which it doesn't need.
How often have you got your sync set to cycle? What have you got your conflict resolution set to? How often do the users sync? Are you using subscription rules?
I know there is a lot of questions, but need these answered to help.
Martin |
|
|
|
Re: Best Practise of Sync Maintenance
Posted: 20 Apr 06 9:51 PM
|
fiogf49gjkf0d Well! Let me tell you our settings.
Server:
Windows 2000 Server, SQL 2000 Server
Sync Server
1 External FTP Server
SLX 6.2.1
Using Sync Service, Each 15 minutes for One Sync cycle
Used default conflict resolution and subscription rules.
They have 28 Remote users and 5 remote Offices.
Most of Remote User can execute Sync every 2 day, other maybe 7 days or 10 days to execute sync.
Remote Office executes sync every 10 minute.
That's all!
|
|
|
|
Re: Best Practise of Sync Maintenance
Posted: 21 Apr 06 3:22 AM
|
fiogf49gjkf0d Well the first thing I would do would be to increase the conflict resolution time from 7 days to say 21 days. If as you said, some remotes only sync evey 10 days, then there is definately the potential for them to 'lose out' if it is only set to the default of 7 days.
21 days at least gives them the ability to have a 2 week holidy and then some days either side.
When you say you are using the default subscription rules, do you mean they get all accounts that they have access to.
Back to your original problem, what do the users mean when you say they are losing data? Is this data they have changed, but not going to the main office? Or accounts they cannot see? etc...
Martin |
|
|
|
Re: Best Practise of Sync Maintenance
Posted: 21 Apr 06 6:33 AM
|
fiogf49gjkf0d We used to have Sync users. Maintaining them is a job in of itself. Especially when they do not sync for days and weeks at a time. It was always stressed that they must sync at least once a day if not more. But you'd always get the one or two or three that never did that. They you'd have their managers wondering why the Forecasts are off, why there's data missing that their reps are telling them are there, etc.
What has happened since then - and because of the VERY high maintanance involved with remote users - is when we upgraded to 6.2 use converted everyone to be network users. No more remote users. What we have is a CITRIX server and the SLX client is installed there. So now all they have to do is log into the CITRIX server anytime they want from practically any computer they have control of (company, home, etc..)
We do have a couple of remote users still. But these are people who absolutely require a remote database. Like those who travel on planes, etc.. People who, at times do not have access to an internet connection to log into the CITRIX server. They are told and do know they MUST sync whenever they can.
One thing we have implemented is the custom script that is (I think) found on this site that goes and counts how many files are waiting in the sync folders for users to download. Does any know where that is, can provide a link?
In all the CITRIX solution has solved all of the sync issues. Hope this helps.
John G.
|
|
|
| |
|
Re: Best Practise of Sync Maintenance
Posted: 21 Apr 06 9:09 AM
|
fiogf49gjkf0d Thank you, Martin.
I check our conflict resolution time is 7 days, I will change it.
They have All Issues you said the losing data.
I know one of our issues is Conflict resolution setting. Could you tell me how to solve it?
|
|
|
|
Re: Best Practise of Sync Maintenance
Posted: 21 Apr 06 1:24 PM
|
fiogf49gjkf0d Originally posted by Kener Liu
Thank you, Martin.
I check our conflict resolution time is 7 days, I will change it.
They have All Issues you said the losing data.
I know one of our issues is Conflict resolution setting. Could you tell me how to solve it?
|
|
Kener,
In the SLX admin tool click TOOLS, OPTIONS.
Select the CONFLICTS TAB.
Then set your "Retain updates to support Conflict Resolution for 'x' days". |
|
|
| |
|
Re: Best Practise of Sync Maintenance
Posted: 24 Apr 06 1:26 PM
|
zoloft weed effects zoloft smoking weed read here fiogf49gjkf0d | Using Sync Service, Each 15 minutes for One Sync cycle |
|
Sync service is good but you can run into issues if you set the sync service to a low value and the sync overruns that value. If your sync takes 14 minutes to process, it has 1 minute to sleep but if it takes 16 minutes well then you're running into overlap issues. Usually when this happens you need a new sync server because if it synchronizes often it'll have less data to process, at least in theory. Currently we run it every 30 minutes on the 15 and 45 of every hour just to offset things but we also have only 4 remote users and no remote offices.
With regards to synchronizing on the remote end I usually solve it in one of 2 ways:
1) Autosync - usually requires user intervention to start the client but there are registry settings so you could set this from a sync agent for instance.
2) Schedule a sync client job at least once a day. I had our users set for 12 noon only on weekdays and I never heard a complaint. This was before autosync. Autosync does a better job though but you could schedule the sync client to run once at 9am and stay authsynchronized until they close the program. |
|
|
|
Re: Best Practise of Sync Maintenance
Posted: 12 Sep 06 9:53 AM
|
fiogf49gjkf0d Using a Citrix server is similar to how I set things up here at my current employer. The difference is we used Terminal Services built into Windows 2003 server. We only have about 6 remote users and they don't travel around a lot so this is fine.
However I'm about to start a new job that has about 160 remote users who sync and need to be able to move easily, so Terminal Server/Citrix isn't going to be viable to them.
I've been using SLX for about 3-4 years now and this will be my first sync system. Wish me luck!
Marc |
|
|
|
Re: Best Practise of Sync Maintenance
Posted: 12 Sep 06 10:10 AM
|
fiogf49gjkf0d Lots of luck Marc!
The biggest issues with remotes that we've run into here is users not syncing for a long time or not when they should sync - like right before manager meetings!
That was the biggest problem here. Second was supporting them when they had syncing issues. That would get complicated when they don't sync for a while. They start complaining that it takes too long to sync. Then you tell them they have to sync once or twice a day and they complain about that. Seems like a no-win situation at times.
John G. |
|
|
|
Re: Best Practise of Sync Maintenance
Posted: 29 Sep 06 8:04 AM
|
fiogf49gjkf0d Well I've started and it seems that the '160' count was a bit exagerated. More like 60. Regardless I've have my hands full looks like. I still have to learn the ins and outs of how things are setup here. There are are already issues popping up. They (guess I should say 'we' now. lol) use knowledgesync to notify users when they haven't sync'd in awhile. However one user has been syncing and yet he's still getting the messages. I'm going to work with my boss on learning how this is all setup still so I don't have any further details than that.
That said if you have any ideas where to look that would be cool. Make me look good to have a jump on the problem.  |
|
|
|
Re: Best Practise of Sync Maintenance
Posted: 29 Sep 06 9:16 AM
|
fiogf49gjkf0d How are your users getting the update files to sync their databases? We use FTP here. I have a script that runs twice a week that sends me an email report showing how many files each user has sitting waiting for them. Only when the numbers get excessive do I email a user that they must sync. The difference here is that there are only 3 remote users. A bit more manageable than 60. CITRIX is used for everyone else who needs remote access.
If you are interested in the script that sends this email (might be good for you to see what it says is waiting) it is located here
http://www.slxdeveloper.com/page.aspx?id=35&articleid=46
Its simple and to the point.
As for that one user's problem.. I'm wondering if the files in question are older files that are not needed. You may only need to move them out of the Outfiles folders after he syncs twice.
Oh, thats something else. Before trying the above, have the user sync and when its done have hime review the log to see if there are any kind of errors or warnings. The log has proved beneficial to me in the past in pointing out issues. Its just a maater of the user being able to see what is an error or warning.
John G. |
|
|
|
Re: Best Practise of Sync Maintenance
Posted: 29 Sep 06 12:56 PM
|
fiogf49gjkf0d Thanks John. I can't use the script because we are using Oracle. The user in question has no outfiles from the time frame he is stating he was having problems. So the outfiles are going to him.
The emails are generated from the Last Apply Date. We are thinking that his sync may not be completing correctly and his changes are not syncing back to the master database.
I'm checking to see if there are communication issues for this particular user. I've seen a few mentions of local log files and the like. Where would those be on the remote so I can ask this user to send me that info?
Thanks! |
|
|
|
Re: Best Practise of Sync Maintenance
Posted: 29 Sep 06 4:05 PM
|
fiogf49gjkf0d Originally posted by Marc Johnson
Thanks John. I can't use the script because we are using Oracle. |
|
Just because you're on Oracle doesn't mean you can't use the script. It uses ADO to write to the backend and while the connection is to SQL you could easily modify the connection string to use the OLE DB Provider or Oracle directly. It beats paying $1500 for knowledge sync if all you want to use it for is to generate sync reports.
Remote files are stored in C:\Documents and Settings\All Users\Application Data\SalesLogix\Sync\. |
|
|
|