|
Re: If most recent backup is not level 0, recovery fails to bring back all files when directories have been renamed
2006-03-08 13:38:19
--On March 8, 2006 11:34:16 AM +0000 Dave Ewart <davee AT ceu.ox.ac DOT uk>
wrote:
Thoughts/opinions here? BTW the AMANDA server runs Debian/Woody
(2.4.2p2-4) and the client being backed up above runs Debian/Sarge AMD64
(2.4.4p3-3).
It could very well be b -- if it is it's not amanda, it's tar. The backup
program is responsible exclusively for what does and does not get backed
up. Amanda just communicates a level/last backup date/file list to use.
Depending on the dump/backup program. I know that a new tar version in
sarge atleast before the security update taht just went out is broken
anyway. It doesn't create valid archives a lot of the time, you'd be
better off installing a backported tar from unstable, or rebuilding the one
in oldstable and using that. Google around for invalid base64 or
obsolescent base64 header skipping to next archive (i think that's right)
if you haven't seen the error message yet.
Cheers,
Dave.
--
Dave Ewart
davee AT ceu.ox.ac DOT uk
Computing Manager, Cancer Epidemiology Unit
Cancer Research UK / Oxford University
PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
Get key from http://www.ceu.ox.ac.uk/~davee/davee-ceu-ox-ac-uk.asc
N 51.7518, W 1.2016
--
"Genius might be described as a supreme capacity for getting its possessors
into trouble of all kinds."
-- Samuel Butler
|
| <Prev in Thread] |
Current Thread |
[Next in Thread> |
- Re: If most recent backup is not level 0, recovery fails to bring back all files when directories have been renamed, (continued)
Re: If most recent backup is not level 0, recovery fails to bring back all files when directories have been renamed,
Michael Loftis <=
|
|
|
