Hans van Zijst wrote:
"Restore can get confused when doing incremental restores from dumps that
were made on active file systems."
Of course I make backups of active file systems. If this really is the
problem, I can't imagine I'm the only one who ran into it. Or am I just the
only one who's ever tested a bare metal recovery? ;)
AFAIK, this wouldn't have the effect of the message "Incremental dump
too low". Because dump dumps the diskblocks themselves, an active
filesystem could screw up the dumpprocess itself. The restore command
would get confused, but not about deciding which level it expects.
The restore process should leave a file "restoresymtable" in the root
directory to pass information between incremental restore passes.
Could it be that such a file was restored from the level 0,
overwriting the current one and indicating that a level 2 or more
was expected?
ps. I switched to tar a long time ago, mainly because I run a mixed
environment and I need to be able to restore onto a completely different
architecture.
--
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 *
***********************************************************************
|
