backup systems. (Use Amanda!!)

[david at thekramers.net (David Kramer)]

On Friday 11 April 2003 11:41 am, Derek Martin wrote:
> On Fri, Apr 11, 2003 at 12:51:17AM -0400, John Abreau wrote:
> I don't see that...  How would you know if an important file has been
> modified, and thus needs to be backed up?  If you did this only once a
> month, an important file might be modified the day after you did it,
> but your procedure wouldn't notice for another month, leaving around
> 29 days for that file to get hosed.

I think the best way to get the functionality you want is to drive the file 
list with the "find" command, and use the "-newer" option.  Every time you 
run your incremental backup, you use -newer in conjunction with some flagfile 
somewhere, and when you finish, touch that flagfile.  The next run will only 
back up files changed since the last backup.

If you want to be EXTRA SOOPER SAFE, touch a different file in the beginning, 
and mv that file to the flagfile when the backup is done.  That way files 
changed during the backup process will get backed up during the next run.


-------------------------------------------------------------------
DDDD   David Kramer                           http://thekramers.net
DK KD  "On two occasions, I have been asked [by members of 
DKK D  Parliament], 'Pray, Mr.  Babbage, if you put into the machine
DK KD   wrong figures, will the right answers come out?' I am not 
DDDD   able to rightly apprehend the kind of confusion of ideas that 
       could provoke such a question."            -- Charles Babbage