Search the Community
Showing results for tags 'presync'.
I am trying to sync LARGE folder from a Windows Machine to any other device (at the moment a Raspberry Pi with a USB Drive, but if I get this working it will be any other device). Large is just shy of 3TB. My thinking was that while I have access to USB I could pre-sync the folder by simply copying files over and then running BTSync to mirror any additional changes. Sync of course wanted to overwrite every file on the Pi. I am assuming due to changes in the file attributes triggering sync to replace them. Trying to use Sync across the lan will take roughly a Month and is outside the bounds of my timeframe. My next try was to use a Robocopy /copyall which in theory should make an exact duplicate of the file including attributes (created/modified timestamps etc). Still wants to overwrite the entire contents of the drive. I am a little stumped, and hopefully there is a way to achieve this? I really like Sync and dont want to have to resort to rsync and chron to automate mirroring my drive. tl:dr How do you manually copy files from a source directory to a target directory and then have Sync maintain them as mirrored without overwriting every file in the target. PS: Apologies if this is a trivial question. I'm new to sync, and spent most of yesterday on Google, and these Forums trying to figure this out.
It would be really really flexible if after BTSync figures out that it has completed syncing a FOLDER let's say, that for that FOLDER you can specify a command to run after the sync completes. A wonderful use would be to maybe run a script that does a GIT ADD/COMMIT/PUSH on the FOLDER after syncing is done. It creates a world of opportunity to handle all sorts of network and peer arrangements that you may not have thought of. And since there is a PostSync, I guess if BTSync scans and figures out that a FOLDER is out of sync, you could have a PreSync action trigger as well. I can't think of what I'd do with that, but that's not the point. Creating useful tools is the point. So with the PostSync action calling a Git script, I could log changes with concrete commits that maybe get pushed out somewhere. Sure there is a chance someone copies files and then adds some more changes after BTSync started syncing, but that's OK.. on the other end it would result in 2 (or more) Git commits right after another.