Why TimeWarp - why not use rsync or other tools

Other traditional backup systems suffer (in the authors experience) from several major issues :
1) Weekly full backups of a reasonable sized file system can lead to very large archive files, which can be vey troublesome to get data out of - Extracting a single file can take 30 minutes or more across a network - excluding the time taken to browse through the archive file - and even this browse can be very time consuming.
2) Creation of these large files cannot be interrupted, so Users have to leave their PC on all the time and hope for no powercuts, network failures etc - and any interruption leads to a corrupted archive.
3) Daily incremental archives can also be very large on an active machie, and only capture the updates at one point in time - useless if you need to go back say a few hours to a previous edit.
4) Creation of these lage achives can be a resource hog - so have to be scheduled when the machine is not in-use for othe work.

TimeWarp tackles all of these poblems :
1) Each file has it's own archive - so no more massive files. File restoration is simpler.
2) A persistent queue is kept of file changes that need to be archived - so if the PC is powered off for the night, Timewarp just picks up where it left off.
3) Each and every file change will trigger it's own archive operation, so unless you change a file very often, evey update will be saved, and can be restored.
4) Timewarp will be configurable to limit the amout of resources it uses, so you can continue to use you machine while timewarp keeps your data safe.
5) You can configure how many archives happen in parrallel, limiting your exposure to failures - only one or two file's archive might get impacted - not the whole file system's archive.
6) Since the archives are small - the system can make them as failure safe as possible - the system always makes a backup of the archive first, and then deletes that back up as the last operation - so any interruption wiill leave a backup intact.