mwang: there's rsync version(s?) for Windows, the one I bumped into was a cygwin build... and I try to stay away from cygwin as much as possible. rsync in and by itself isn't enough for backup though, imho - it should be combined with script/whatever to get the same kind of functionality as time machine has. I use
rsnapshot on my linux box, works like a charm.
Block-level backups are cool, but I don't
really need it for the stuff I want backed up. Also, without a filter driver (or something really smart I don't know about), I dunno how they can detect block changes efficiently (comparing to a backed-up version would be stupid). I was mostly excited about the block-level feature because I thougth it would mean a filter driver (I've got a thing for those
)... which would mean the backup app
instantly knowing about file changes in a pretty efficient way.
Haven't had time to play around with Timeline, but it does sound like it's configurability is on the low end - that kinda sucks. And wtf is up with including a web server as part of the application? O_o - takes up ~28MB installed, and seems like a pretty pointless thing to do. Oh, and if explorer is the only interface for restoring backups, then... ugh.
No, it didn't install any driver (inside the Windows directory tree if that's what you mean) according to my log. It has a "BlockLevel.dll" and it puts a ton into the registry. Do you really need a "driver" to do block-level backups? It registered as a set of system services and does its work in the background. Can't it perform block-level backups that way? That seems to be how SpiderOak does it as well.-mwang
Well, for what I know, you need a filter driver (.sys) to detect "X bytes written too ffset Y in file Z" change notification (rather than just getting "file has changed") - unless you can ask Volume Shadow Copy Service or something. If you don't get the "X,Y,Z" notification, afaik you'd have to do a manual compare of the file to a previous version in order to detect modified blocks. This would work, and conserve space, but it's a lot slower than simply writing out blocks you've been previously told were modified.
I noticed blocklevel.dll as well and took a quick look at it, and it's definitely not a driver. Seems to use SQLite for something, possibly to store list of changed blocks?... but I didn't look any deeper than that.