alexmeyer

Members
  • Content Count

    4
  • Joined

  • Last visited

About alexmeyer

  • Rank
    New User
  1. Yikes. Yeah, that's the kinda stuff that I know can happen, period, but especially with a two-way sync. Wouldn't trust one for my use case. And even with the read-only secrets, I'm still quite careful, your story as a case-in-point.
  2. @arcol: while that's an interesting idea, I honestly don't need anything that complex. My main reason for posting this question was to see if anyone else had a similar setup/workflow/etc., and if so, to see how they handle it. I'm thinking that an integrated solution with that level of complexity is probably out of btsync's development scope. @fukawi2: that's a really good idea, and would probably work great if my setup were slightly different. I have mixed OSes for nodes (linux, windows, etc.), which isn't actually that big of a deal. It'd be easy enough to script something similar for each platform. The main problem with that approach though (for me and my setup at least), is that my syncs are one-way read-only syncs from my laptop to the nodes. Since my laptop is my main workhorse machine and the nodes are basically just a large mirrored backup, it's one-way. I wouldn't ever risk doing a two-way sync with the critical project data on my laptop. Don't need it for that kind of use, and way too much room for major issues. I can just imagine something going funky and deleting/corrupting/messing up all my projects on my laptop. So everything else up to that point would work, it just wouldn't sync back the actual deletion of the old files. Otherwise, like I said, it's a good idea. Thanks everybody for the replies so far! -Alex
  3. Hey guys, thanks for the replies. Marko: I know that I can change the 30 day limit, it's more just that the .SyncArchive folder isn't where I'd want the long-term archival of stuff to be. The legit archive stuff would also be mixed in with stuff I've actually intentionally deleted. Just not the ideal setup. nils: I actually don't need any versioning or anything fancy. Basically, when I'm done with a video project (mostly promo videos, etc.), I don't really need the project anymore, but I want to archive it so if I need something in the future, I still have it backed up. Using the nodes as a virtual mirrored raid, basically. Hmm, just tested, and it looks like BTSync handles file moving (cut/paste) operations nicely. I might just use an "archive" folder within my parent sync folder, move old projects into that folder to consolidate the old ones that I want to archive, and then backup and remove that folder on each node. And once those are backed up, then I can remove the stuff from my laptop hard drive. I'm really just trying to figure out the most efficient workflow for all of this.
  4. Hey, love BTSync, and I've been using it for a bit. Trying to figure out some workflow things, and I thought i'd throw this out there and see if anyone else has some different perspectives. My setup: My Macbook Pro with a 750GB hard drive that's my main computer, I do lots of video editing projects, photography, etc. Lots of data being created all the time. And I'm always running short of space on there. And then I've got a couple BTSync nodes (our home 6TB NAS server, an old tower with a 1TB hd sitting at work, etc.) syncing those folders read-only from my laptop. The main thing I want to be able to do with BTSync is keep everything on my laptop continually backed up (which it does wonderfully), but then when I go to archive old projects to make room on my laptop hard drive, I'd love it if the nodes kept the old files and didn't delete anything. So basically using the nodes as a big distributed archival system. I know if I delete stuff from my laptop, the nodes will move the stuff into the .SyncArchive folders, but only for 30 days, and then I'd have to move stuff from that .SyncArchive folder to a safe unsynced folder, repeating for each node, etc. Anyway, just wondering if anyone else is doing anything similar. Basically a one-way sync as a backup, but not syncing deletions. Kinda. Or some alternative to that. Thanks! Alex