🚀 go-pugleaf

Well, after backing up once with Redux, I could not, get this, get it to back
up "changed" files.  I can see no way, and none is outlined in the manual.
The best I could do is script "Check all file older than one day." but that
would leave me with a one day gap between when I made my backup and what was
really on it.  But, I figured that I could live with that for a while, so 
I went ahead to backup and the stupid thing just hung there.  It didn't even
spin the disk in the internal drive (I was running without any INITs since
the program is such a memory hog, though I was trying to back up 100 meg of
stuff.  So I couldn't get Redux to do any incremental backups for me so I had
to start all over again with FastBack.  This time I turned on the "Verify while
writing" option, just to see how slow FastBack could go, and with that it still
only took "149 minutes and 46 seconds...which includes a 5 minute and 34
second wait for user to insert disks."  So that is not too bad.  I can live
with that.  I was hoping that Redux would do more (mainly allow you to backup
files you made the same day as the backup).  But it wouldn't, so I will do it
with FastBack and just uncheck all the files I don't want backed up.

I have never used DiskFit, but I like speed, and data recovery posibility and
with FastBack I get both.  FastBack IS fast, and with its own special format
it will recover something like 1/5 the disk sectors on the disk if they go bad
due to long periods of unuse (after all, the file may have been written right,
and verified, but remember that first disk that all the files on it never
changed and then finally two years later your HD dies and you try and back it
up only to find that it chokes on the first disk and so on....).  FastBack will
help, but not solve cases like these.  (By the way, this has happened to me
before, a real bummer until I started using FastBack.)

So, that is why I throw a third back up program into these wars....

Mark Cookson