realtimesync advice

Get help for specific problems
Posts: 1
Joined: 5 Nov 2012

ender236

howdy all. i tried posting this once before but i think my browser must have messed up or something, so i'm giving it another try.

first, thanks for such an awesome program, ffs rocks!

now to my question. up to now i've just placed a batch file on the user's desktop that they could run and back up their files to the server whenever it was convenient for them. but apparently there is never a convenient time to click that little icon lol. so we had a user's hard drive fail and they hadn't backed up their files. now i'm looking to set up some kind of automated sync process so that we don't have to worry about this sort of thing happening again.

i've been messing with RealTimeSync and it seems highly effective, set it up in the Startup folder and away it goes without the user ever seeing a thing. this is great for desktops, but there is an issue i'm trying to find a way around for laptop users.

the issue is that we have users who travel to other locations within the company, sometimes hundreds of miles away, but i'm afraid that because we're still on the same network and RealTimeSync will still be able to see our server here, it will try to sync files over a huge distance between the facilities.

is there a way to leave rts running, but only sync files when the user is here at our facility? or will rts attempt to sync no matter what, as long as it can see the server it's backing up to? ideally i would like to find a way to make this work without any action on the user's part. the more transparent the process is to them, the better. any advice is greatly appreciated. thanks!
User avatar
Site Admin
Posts: 7279
Joined: 9 Dec 2007

Zenju

RealTimeSync will start monitoring as soon as it sees all directories that have been configured.
There is probably a way to setup some really fancy script, that will only launch RTS if the user is at your facility. What about the simplest solution: Have FFS start when the operating system boots up and/or when it shuts down. During startup you could enable error reporting so that the user can handle them, and during shutdown you would just "ignore" errors (since he's probably in a rush going home anyway).