linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Furness <paul.furness@vil.ite.mee.com>
To: admin <linux-admin@vger.kernel.org>
Subject: Detailed info about backups
Date: Wed, 27 Oct 2004 10:11:52 +0100	[thread overview]
Message-ID: <1098868312.27244.18.camel@zebra.vil.ite.mee.com> (raw)

Hello.

Can anyone give me some pointers for comprehensive information about
tape backups?

A brief bit of background:

I have linux servers running mostly FC2, some RH9 and a couple of RH73.
One of the servers has some autochangers attached - a DLT, an LT01 and
an LTO2. I have scripts which automate which tape to load based on the
day and what's being backed up. Control of the changers is done using
mtx, control of the drives is done with mt, and the backups are done
using xfsdump and dump from remote machines.

The main problem I have is that I seem to be running out of space on the
tape a long time before I've stored anywhere near as much data on there
as the tape should hold - for instance, I'm trying to back up about 150G
on an LTO2 tape which has native capacity of 200G, and it's failing with
a message suggesting the tape is full.

There are a couple of specific things I'm trying to find out; maybe
someone knows the answers to these and can answer me direct :o)    

What does "block size" mean on a tape (DLT and LTO). Is it the same as
old disks, where each file fills up at least one block, even if it's
much smaller than a block? If I make this smaller, will more small files
fit on the tape?

How do I get the tape drive to definitely use it's internal compression
hardware? I don't think it's working and I need it to be. How can I
check this from linux? Some of the auto-changers have displays on the
front that specify whether compression is being used, but others don't.

Is there any way of finding out how much of the tape has been used by a
backup - in terms of actual tape, not in terms of how much data there
was in the backup? I really want to be able to work out how much space
is left on the tape.
 
Answers to any and all of the above questions very much appreciated.

Thanks.

Paul.



             reply	other threads:[~2004-10-27  9:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27  9:11 Paul Furness [this message]
2004-10-27 12:50 ` Detailed info about backups Stephen Samuel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1098868312.27244.18.camel@zebra.vil.ite.mee.com \
    --to=paul.furness@vil.ite.mee.com \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).