[Techtalk] Detect if Dump used multiple tapes for backup.

Conor Daly conor.daly-linuxchix at cod.homelinux.org
Tue Jun 22 15:44:39 UTC 2010


On Tue, Jun 22, 2010 at 04:23:51PM +0100 or so it is rumoured hereabouts, 
James Sutherland thought:
> On Tue, Jun 22, 2010 at 1:31 PM, Conor Daly <c.daly at met.ie> wrote:
> > On Tue, Jun 22, 2010 at 08:03:22AM -0400 or thereabouts, Little Girl wrote:
> >> Hey there,
> >>
> >> Conor Daly wrote:
> >>
> >> > I'm backing up a 300Gb filesystem to an SDLT320 tape and,
> >> > occasionally, the weekly level 0 dump will overflow to a second
> >> > tape.
> >> >
> (snip)
> > Mag tapes are a different kind of storage.  Basically data gets written /
> > read sequentially so there's no real way to interact with a tape.  Depending
> > on the software that wrote the tape, there may be a catalogue stored at the
> > beginning of the tape but there's no real way to know about size stored.
> 
> How does the tape get changed? Presumably, in the overrun case, your
> dump starts writing to tape #1, fills up the 160Gb (after compression),
> then something goes "whoops, out of space - on to tape #2!" Even if
> it's automatic, *something* must be getting told to change the tape for
> the first backup to continue: could you not detect that event from logs,
> exit status or whatever?

There is a script that runs between tapes.  Currently it does nothing and
just returns and dump continues to attempt to write to the same tape.
This repeats a bunch of times before dump gives up.

The filling of tapes is only really becoming an issue for us recently and
it's in the context of updating our backup scripts that I'm trying to
figure out this stuff.

We use a tape library to load up to 8 tapes sequentially.  Currently there
is one tape dedicated to each 300Gb filesystem and another covering the /
/home etc filesystems.

The plan is for dump to call a tape change script when a tape fills and
then to carry on.  Because we do a weekly level 0 followed by daily level
1 dumps to the same tape, we must wind the tape to end of data for each
level 1.  In the case that tape 1 is full and the end of data is on tape
2, I need to figure out how to detect that.  I'll have to do some more
testing, particularly for the case where we actually change the tape when
it fills to see is there any flag readable from the tape.

Otherwise I'll have to log the status in the filesystem instead...

Conor
-- 
Conor Daly <conor.daly at cod.homelinux.org>
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/G/S/O d+(-) s:+ a+ C++(+) UL++++ US++ P>++ L+++>++++ E--- W++ !N
PS+ PE Y+ PGP? tv(-) b+++(+) G e+++(*) h-- r+++ z++++ 
------END GEEK CODE BLOCK------
http://www.geekcode.com/ http://www.ebb.org/ungeek/


More information about the Techtalk mailing list