21–30 of 106 posts
Earlier quoted context omitted.
You do snapshots on your target.
Sure, filesystems with snapshotting and deduplication capabilities let you use much simpler tools to implement backups. I don't think they're common in consumer-level storage devices, though.
Right after I saw the animated details (you know, the one that pops up when you click "Change") I wanted to see its source code :/
Can you please tell us what language? and/or 3rd party controls are you using? Please?
I'm guessing it might be on the work in progress page but the page looks too detailed, so I have bookmarked it for when I have more time than I currently do.
Earlier quoted context omitted.
Actually, I was thinking of rolling hourly/daily/weekly backups and I didn't understand how I would set that up with your program. Would I have to sync the same source to multiple destinations on different schedules? That seems inefficient compared to e.g. http://www.mikerubel.org/computers/rsync_snapshots/ Please don't get me wrong, I'm not trying to denigrate the software you've written! I was just surprised to see…
Why is it that you are surprised to see it marketed as a backup tool? I know about bup , thanks.
It looks like your software protects to some extent against accidental deletions of files, which puts it far ahead of most file sync tools. But, if it's still possible to accidentally delete the contents of a file or otherwise corrupt it, then it's not a backup.
We usually end up recommending Acronis TrueImage, which is in the same price range as your software. I'd happily recommend your software instead, since TrueImage is clunky and slow, but without archiving it doesn't count as backup software.
(For one real-world example: we had a corporate client get hit by Cryptolocker. It looks like in this case your software would've automatically copied the changed files over to the backup directory; is this the case, or am I missing something?)
How does it compare to http://freefilesync.sourceforge.net/ ? Apart from the delta copying the feature list sounds similar. I find the FreeFileSync UI quite usable.
Faster bulk copying, lighter build, lighter on resource usage, removable device tracking, much better UI (it's subjective, of course, but just try it out and see for yourself). Formal backup planner, dry runs, native support for running as a service with separate engine and UI processes. -- edit -- Let me give an example of what I mean by "much better UI". Bvckup 2 has a hierarchical log viewer [1] and this thing doe…
What a great looking website!
Earlier quoted context omitted.
Why is it that you are surprised to see it marketed as a backup tool? I know about bup , thanks.
We occasionally get questions from clients about using some file sync tool or another for their backups, and we are very firm with them: file sync is not a backup . It looks like your software protects to some extent against accidental deletions of files, which puts it far ahead of most file sync tools. But, if it's still possible to accidentally delete the contents of a file or otherwise corrupt it, then it's not a…
Every backup has a set of risks that it mitigates. If the goal is to mitigate human errors, then, yes, versioning/archiving is a must. However if someone just needs to have a daily snapshot of their photos and documents to protect them against fire of theft, then you can certainly call it a file sync, but it still is a backup. To each his own. "Backup" is not an exact term, but rather a range of data protection techniques.
All that said, the archiving is coming up.
Earlier quoted context omitted.
Faster bulk copying, lighter build, lighter on resource usage, removable device tracking, much better UI (it's subjective, of course, but just try it out and see for yourself). Formal backup planner, dry runs, native support for running as a service with separate engine and UI processes. -- edit -- Let me give an example of what I mean by "much better UI". Bvckup 2 has a hierarchical log viewer [1] and this thing doe…
Why would I want to delve into my backup run's log files? Seems pretty counter-intuitive as it's something you expect to work out of the box, not something that you'd have to debug and have issues with.
Earlier quoted context omitted.
We occasionally get questions from clients about using some file sync tool or another for their backups, and we are very firm with them: file sync is not a backup . It looks like your software protects to some extent against accidental deletions of files, which puts it far ahead of most file sync tools. But, if it's still possible to accidentally delete the contents of a file or otherwise corrupt it, then it's not a…
This reminds me how every time someone posts a salad recipe to /r/cooking the whole discussion inevitably converges to the topic of a salad without a mayo not being a real salad ... just as it is not a salad with the mayo :) Every backup has a set of risks that it mitigates. If the goal is to mitigate human errors, then, yes, versioning/archiving is a must. However if someone just needs to have a daily snapshot of th…
We're trying to narrow the range of things that people consider a "backup" so that they don't get wildly disappointed in the future. This isn't a matter of taste.
> All that said, the archiving is coming up.
Fantastic!
This is probably the nicest looking Windows application I have seen in a while. The website is pretty slick too. This is the kind of detail that you usually get to see for Mac applications. Great Job. Seriously. Right after I saw the animated details (you know, the one that pops up when you click "Change") I wanted to see its source code :/ Can you please tell us what language? and/or 3rd party controls are you using…