From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: more about backups
Date: Tue, 25 Apr 1995 08:48:48 -0400 [thread overview]
Message-ID: <19950425124848.oWRiXCVJA_FqhVwI8R4AfYf3pU7Jo3yTHbSznK16LgY@z> (raw)
>>if you have just one machine (at home, say.) Tar doesn't
>>do multivolume dumps, so I guess you just need a big DAT
i haven't had to worry about this yet, since
my scsi tape is currently big enough to hold the file system data,
but here is what i'll probably do at home when my disc usage increases.
use mkfs -a rather than tar. i think you probably want to do this anyway
for plan 9 backups (restore using mkext). you can then dump /usr and
the rest of / (say) to separate tapes
by using an appopriate proto file for mkfs for each tape.
reply other threads:[~1995-04-25 12:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19950425124848.oWRiXCVJA_FqhVwI8R4AfYf3pU7Jo3yTHbSznK16LgY@z \
--to=forsyth@plan9.cs.york.ac.uk \
/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).