[clug] Tape spanning with Amanda

[Alastair D'Silva]

Make sure you turn off async writes - I had the same issue with mbuffer, and
disabling async fixed it.

--
Alastair D'Silva           mob: 0423 762 819
Networking Consultant
New Millennium Networking  web: http://www.newmillennium.net.au
skype: alastair_dsilva     msn: alastair at d-silva.org
blog: http://alastair.d-silva.org


-----Original Message-----
From: linux-bounces+clug=d-silva.org at lists.samba.org
[mailto:linux-bounces+clug=d-silva.org at lists.samba.org] On Behalf Of Chris
Smart
Sent: Monday, 13 October 2008 11:11 AM
To: CLUG
Subject: [clug] Tape spanning with Amanda

Am currently using Amanda to backup some data onto an IBM LTO3
library, 400GB tapes uncompressed. It all works well, except that
restoring a file that has spanned two tapes returns an different
md5sum to the original. *Gasp*

>From memory, I have a file split size of 4GB. The Amanda log says "ran
out of room, trying new tape" or something to that effect. I would
have thought that Amanda would not write that 4GB tarball to the tape,
if it calculated that there wasn't enough space left (at least that's
what the docs lead me to believe) - but it appears to write it anyway,
run out of space, and move onto the next tape.

Has anyone run into this issue before? I'm assuming that it's
something wrong with my config re spanning / tape size set up - then
again it could be normal behavior! :o

Cheers,
-c
-- 
linux mailing list
linux at lists.samba.org
https://lists.samba.org/mailman/listinfo/linux