From: Paul Furness <paul.furness@vil.ite.mee.com>
To: Paul Kraus <pkraus@pelsupply.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Tar Backups
Date: 01 Oct 2002 08:40:37 +0100 [thread overview]
Message-ID: <1033458038.10135.15.camel@Zebra> (raw)
In-Reply-To: <002601c268b6$a09f0d70$64fea8c0@pkrausxp>
Hmm, you could try a slightly different approach.
Obviously, I don't know the layout of the data that you are backing up,
but assuming that it's in a number of distinct areas you could use
something like dump or tar a number of times, thereby breaking your 13GB
into a number of smaller files. This means you can fast-forward to the
sub-section you want and only have to read through a smallish amount of
data.
For example, if you were backing up the users' home directories, you
would have something like this:
-home
|
+ paulk
| |
| +various directories
|
+ paulf
| |
| +various directories
|
and other stuff...
You could write a simple script that backs up everything under 'paulk'
and then in a separate file backs up everything under 'paulf' without
rewinding the tape in between (you do this by specifying the tape device
to use with tar; /dev/stX are scsi tape devices, but /dev/nstX are
_non-rewinding_ tape devices).
Then, when you later want to restore a file from under 'paulf', you can
wind the tape forward by the number of files you need to before starting
to read the data.
Granted that this is a little more complex to set up than what you are
currently using, but in the long run it could save you a lot of time.
More simply, of course, it's pretty cheap to buy another hard disk and
back up to that as well as the tape. Then, you keep the tape in the
cupboard / drawer / safe, and you can use the disk for getting back
single files quickly. It doesn't matter if the disk is over-written
every couple of days, since you have the tapes for longer term backup.
Of course, if the data is _really_ important data, and you often have to
restore parts of it, you might want to look at something else - either a
specific backup package (possibly even a commercial one) or,
If you want to talk about this in more depth, mail me direct.
Paul F.
On Mon, 2002-09-30 at 20:21, Paul Kraus wrote:
> Is there a way to have an index written? I am making 13gb backups and it
> takes forever to simply restore because it has to read each and every
> single file on the tape. This is actually on my sco box but the question
> is relevant because I plan on moving the file server to a red hat
> machine.
>
>
> Paul Kraus
> Network Administrator
> PEL Supply Company
> 216.267.5775 Voice
> 216-267-6176 Fax
> www.pelsupply.com
--
Paul Furness
Systems Manager
2+2=5 for extremely large values of 2.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2002-10-01 7:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 19:21 Tar Backups Paul Kraus
2002-09-30 19:39 ` Ray Olszewski
2002-09-30 19:48 ` Paul Kraus
2002-09-30 20:12 ` pa3gcu
2002-09-30 20:35 ` Paul Kraus
2002-09-30 20:52 ` pa3gcu
2002-10-01 1:01 ` Jude DaShiell
2002-10-01 20:01 ` James Mohr
2002-10-01 7:40 ` Paul Furness [this message]
2002-10-02 16:38 ` James Hatridge
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=1033458038.10135.15.camel@Zebra \
--to=paul.furness@vil.ite.mee.com \
--cc=linux-newbie@vger.kernel.org \
--cc=pkraus@pelsupply.com \
/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