Real-Time Sync stops

[Netkeys]

I'm testing BestSync for use on a Windows 2008 server doing real-time sync to a backup NAS server.

After creating the job and setting it to either run normally or as a service it seems to start and works fine. But after a few hours it stops and even stopping and restarting the job will no longer sync. It doesn't find any changes even though using directory compare software there have been changes.

I deleted and recreated the job 4 times before it finally started to sync the changed files. I've tested this same job on a Windows 7 pro machine as well as a Vista workstation and they all showed the same problem. Start of fine but stop after a short while and will not continue even after a restart. On all machines I've tried it as both a standard job and also as a service and it doesn't seem to make a difference. The problem is the same.


Ron

[RiseFly]

Please click the "Option""View Log File" menu to show the log data, to see if there is any error happens.

[Netkeys]

Here's the end of the log file where it shows no activity after 4-11 until today when I opened the program. Until now it was running as a service and was showing in the notification area of the task bar.

BestSync 2011 64 bit version is running on a Windows 2008 standard server 64 bit version. This is a production server is runs 24/7 and has not been rebooted since installing and configuring BestSync.

Start of Log File:

APP:2011/04/08-23:08:40,Start task:D:\ ==> I:\
APP:2011/04/08-23:08:40,Start task manually.
APP:2011/04/08-23:08:41,Task Result: D:\ ==> I:\ (Success=0, Failed=0)
APP:2011/04/08-23:08:41,End Task -D:\ ==> I:\
APP:2011/04/08-23:08:41,Start Monitor-D:\ ==> I:\
APP:2011/04/08-23:08:41,Monitor Change--CreateFile successfully!-D:\ ==> I:\
APP:2011/04/08-23:08:41,Monitor Change--CreateFile successfully!-D:\ ==> I:\
APP:2011/04/08-23:08:44,Monitor: Full sync D:\ ==> I:\,
APP:2011/04/08-23:08:45,Monitor sync: Switch Backup Folder. D:\ ==> I:\
APP:2011/04/08-23:18:45,Monitor: Full sync D:\ ==> I:\,
APP:2011/04/08-23:23:21,Monitor sync: D:\ ==> I:\, Processed 3 changes.
APP:2011/04/08-23:23:40,Monitor sync: D:\ ==> I:\, Processed 3 changes.
SVC:2011/04/08-23:30:00,Service started.
SVC:2011/04/08-23:30:00,***** BestSync Service start ****
OS Version:Windows Server 2008 Standard Edition, 64-bit Service Pack 2 (build 6002)
BestSync Version:Ver6.1.0.8
SVC:2011/04/08-23:30:00,Reload Setting File.
SVC:2011/04/08-23:30:00,Load setting file [C:\ProgramData\RiseFly\BestSync 2011\service.fsf] is successfully.
SVC:2011/04/08-23:30:00,Drive is not ready[I:\]
SVC:2011/04/08-23:30:00,Start Monitor-D:\ ==> I:\
SVC:2011/04/08-23:30:00,Monitor Change--CreateFile successfully!-D:\ ==> I:\

End Of Log File:
APP:2011/04/11-12:29:30,Monitor: Full sync D:\ ==> \\STORAGE\Server_Copy_D\,
APP:2011/04/11-12:31:22,Task Result: D:\ ==> \\STORAGE\Server_Copy_D\ (Success=233, Failed=0)
APP:2011/04/11-12:31:37,Monitor sync: D:\ ==> \\STORAGE\Server_Copy_D\, Processed 4 changes.
APP:2011/04/11-12:31:55,Monitor sync: D:\ ==> \\STORAGE\Server_Copy_D\, Processed 1 changes.
APP:2011/04/11-12:41:23,Monitor: Full sync D:\ ==> \\STORAGE\Server_Copy_D\,
APP:2011/04/11-12:47:19,Monitor sync: D:\ ==> \\STORAGE\Server_Copy_D\, Processed 1 changes.
APP:2011/04/11-12:47:35,Monitor sync: D:\ ==> \\STORAGE\Server_Copy_D\, Processed 1 changes.
APP:2011/04/11-12:53:09,Monitor sync: D:\ ==> \\STORAGE\Server_Copy_D\, Processed 5 changes.
APP:2011/04/11-12:53:13,Monitor: Full sync D:\ ==> \\STORAGE\Server_Copy_D\,
APP:2011/04/11-12:55:11,Monitor sync: D:\ ==> \\STORAGE\Server_Copy_D\, Processed 1 changes.
APP:2011/04/11-12:56:33,Monitor sync: D:\ ==> \\STORAGE\Server_Copy_D\, Processed 3 changes.
APP:2011/04/11-12:56:51,Monitor sync: D:\ ==> \\STORAGE\Server_Copy_D\, Processed 1 changes.
APP:2011/04/17-12:37:40,***** BestSync start ****
OS Version:Windows Server 2008 Standard Edition, 64-bit Service Pack 2 (build 6002)
BestSync Version:English Version Ver6.1.0.8
APP:2011/04/15-11:57:41,***** BestSync start ****
OS Version:Windows Server 2008 Standard Edition, 64-bit Service Pack 2 (build 6002)
BestSync Version:English Version Ver6.1.0.8
SVC:2011/04/15-03:28:20,Service started.
SVC:2011/04/15-03:28:20,***** BestSync Service start ****
OS Version:Windows Server 2008 Standard Edition, 64-bit Service Pack 2 (build 6002)
BestSync Version:Ver6.1.0.8
SVC:2011/04/15-03:28:20,Reload Setting File.
SVC:2011/04/15-03:28:20,Load setting file [C:\ProgramData\RiseFly\BestSync 2011\service.fsf] is successfully.
SVC:2011/04/15-03:31:26,Create VSS Successfully--[D:\].
SVC:2011/04/15-03:31:26,Start task:D:\ ==> \\STORAGE\Server_Copy_D\
SVC:2011/04/15-03:31:26,Start task by schedule.
APP:2011/04/17-12:52:31,***** BestSync start ****
OS Version:Windows Server 2008 Standard Edition, 64-bit Service Pack 2 (build 6002)
BestSync Version:English Version Ver6.1.0.8

[RiseFly]

If the task is synchronizing with the network drive, please confirm if you have set a login account in the task setting.
Please refer to the following q&a page:
http://www.risefly.com/fseqna.htm#SyncWithNetDrive

[Netkeys]

The server is syncing to a network NAS. No login is required to access the NAS.

It connected in the beginning but it just stops with no errors it just doesn't do anything.

When I changed from a service to a normal job and manually ran the job manually it still would not sync.

It's configured as a one way mirror type of sync for backup purposes.

Copy changes on source (windows server) to NAS

The same problem happened when doing the backup to a USB attached external HD where it was all running on one computer.

Let me know is you have any more questions.

[RiseFly]

If a task is run as Windows Service, and it is synchronizing with a network drive (folder), the login account is necessary, otherwise no none will login the network drive, and the folder will not be accessable. If both folders are network folder, you need to set the login account for the bith folders.
Are you using the latest ver 6.1.12? From version 6.1.10, there is a bug that might cause a task not be stopped correctly, thus can not be started again. The version 6.1.12 has corrected the bug.