I would like to know how to configure Amanda to do differential backup, that is make full backups once every week or so and then let the daily backup only backup changes since the last full backup. I
Author: Joshua Baker-LePain <jlb17 AT duke DOT edu>
Date: Fri, 9 May 2003 15:52:50 -0400 (EDT)
The question is, why? Amanda can schedule this all quite well, and it's a lot less effort on your part to let it handle this. Look at the 'nofull' and 'incronly' dump strategies in the example amanda
man for don't If we are talking about typical filesystem which is changed a little, day by day, we should based on Amanda. She is doing her job perfectly! This is probably the best suggestion for Pe
Author: Joshua Baker-LePain <jlb17 AT duke DOT edu>
Date: Fri, 9 May 2003 16:21:58 -0400 (EDT)
"Only" level 9?! At that point, you're going to need to read the backups off *10* tapes to get your whole filesystem back. Thanks, but no thanks... -- Joshua Baker-LePain Department of Biomedical Eng
Joshua, Forget for a moment a typical OS filesystem and users' data, please. I was writing about pure data filesystem, where server is creating thousands of files (~5000), several GB quantity daily (
Author: Gene Heskett <gene.heskett AT verizon DOT net>
Date: Fri, 9 May 2003 17:17:53 -0400
I'll byte. 4 questions for this old mans edification. 1. To what does one "anchor" the backup to if the level 0 is never done. It seems to me that even for all the so-called incremental levels, there
Gene & Joshua, The Gene's post passed mine, where I have tried to explain my case. The files are already compressed so I need to use 'compress none' within dumptype. I have played with 'nofull' and '
Author: Joshua Baker-LePain <jlb17 AT duke DOT edu>
Date: Fri, 9 May 2003 17:18:16 -0400 (EDT)
Well, no "traditional" backup tool is designed for such a situation, really. It seems to me that a quick script using find and tar would work quite well for this situation, though. -- Joshua Baker-Le