Hans van Zijst wrote:
Funny that you mention tar. The reason why I chose dump is that dump was
supposed to handle open files better than tar. Plus, I don't like the idea
of atime being updated because of a backup.
Tar and dump handle open files just as bad. Or maybe tar is a little
better in that the gnutar does not generate a corrupt archive.
Only the active file itself could be in some inconsistent state.
Dump could generate a corrupt archive that makes restore crash/dump
core (although, I've never seen this happen -- but I only use dump
sporadically).
To avoid modifying the atime, some of my systems do backups using
filesystem snapshots, and the backup is made on the readonly, stable
copy of the snapshot. No more problems with modification of atime
nor active filesytems/open files.
--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
|
