🚀 go-pugleaf

[]

I am using Redux to do my backups and have run into some strangeness.
When I initially did the first backup, I had ALL FILES checked.
Redux backed them all up.  When it came time to do incrementals, Redux
informed me that some of my files had changed.  Well, I knew that the
changes were insignificant, even useless (e.g., a file which had gotten
nVIR and then had it removed *after* the initial backup) so I removed the
check from these files.  When I finally did need to do a restore, all of
these files were gone.  

The question:  When I meant to tell Redux "don't bother with the incremental
on these files and just go with the originals" did Redux think I meant "ah,
he wants to nuke these files from the backup set."  If so, how can I 
get Redux to ignore files like those I mentioned above?

Second question:  What other backup programs are there which are
comperable to Redux?  Redux seems to always create larger and larger sets.
When I had removed about 8 MB of junk from my HD and added ONE new large file
(700K) the backupset GREW by one disk when (I thought) it should have shrunk
by at least 6.  Whose fault is that?  Am I again not using it correctly?

eMail replies, I'll post to the net if there is interest/news.

-Thanks in advance

-ajw


Andy J. Williams '90   |           <hello>           | ack@dartvax.dartmouth.edu
31 North Main Street   |  set $NAME='inigo_montoya'  |        Systems Programmer
Hanover NH, 03755      |     You kill -9 my ppid     | Kiewit Computation Center
603-643-2177           |        prepare to vi        |         Dartmouth College