¹excepting the recent change where a "developer mode" can be activated, but that still doesn't make them useful on an end user's machine, or to an end user.
Also this page badly needs a ToC.
Are you running rdiff-backup in cygwin? How do you find it deals with the ntfs ACLs? I'm looking for a way to do incremental full-disk backups that leave the files on disk in a "natural" state, with their original pathnames/ACLs/ADSs and not in some weird archive format. Although I suppose rdiff doesn't count as "weird" being as its open source and well supported.
TBH I'm quite liking the look of the windows built-in backup function, I like the idea of the shadow copy service and storing disk images as VHLs. Booting into the backups in virtualbox sounds cool.
The problem is that the "Previous Versions" get stored on the primary drive, not the backup drive, eating into my free space. Unfortunately one can't set it to use the empty space, it wants to preallocate. You also can't set a time interval, only a percentage of the volume.
As far as I can tell consecutive VHL images don't get stored as diffs or anything, they're separate, meaning I'd really only get one at a time.
Oh, come back Time Machine, all is forgiven.
If this is important to you (as it is to me), it's worth noting that Cygwin supports creating native NTFS symlinks, and you can use the good old GNU ln (same one you'd use on Linux!) to do so. There are some caveats, but it should at least attempt them. See the documentation: https://cygwin.com/cygwin-ug-net/using.html#pathnames-symlin...
(And let's not mind that NTFS is complicated enough that almost all native Windows tools won't backup it either. Your best bets are wimlib or dism...)
https://technet.microsoft.com/en-us/sysinternals/bb896768.as...
https://technet.microsoft.com/en-us/library/cc753194(v=ws.11...