From: Jerry James Haumberger <jerryjh@imt.net>
To: linux-newbie@vger.kernel.org
Subject: tar for "full" floppy backup?
Date: Mon, 9 Dec 2002 07:00:11 +0000 (UTC) [thread overview]
Message-ID: <200212090658.XAA16146@cu.imt.net> (raw)
>> As it stands, it's possible to backup to multiple floppy
>> disks with tar, but these cannot be compressed during the
>> archival process.
>Why not use tar twice: first with -zcf to make a compressed
>archive and then with --multi-volume to write the archive
>to floppy. Of course to retrieve it, you will also have
>to use tar twice: first with --multi-volume to reconstruct
>the archive and then with -cvf to unpack it.
What result would you get with that method if you wanted to
review the multiple archive's details with -->
tar --multi-volume -tv --file=/dev/fd0 > backup.log
-->? Not that much detail. Just that one big file.
The tar backup routine I've described with your BasicLinux
distribution barely took over six floppy disks, yet I still want
to check out the results, or at least have them available. (And
I've done just that -- I can review the results of that backup
from a file that had the results directed to it while using the
tar command above.)
For quick backup of important files, though, I'm using the following
script -- perhaps a little "busier" than it needs to be, but then
I'm just a "linux-newbie"... ;-)
-----------------------
cd /home
mount /dev/fd0 /fd14
tar cvpf hot_backup.tar /etc /home /root /var/eznet
gzip hot_backup.tar
rm /fd14/hot_backup/hot_backup.tar.gz
mv hot_backup.tar.gz /fd14/hot_backup
umount /fd14
echo "***FINISHED***"
-----------------------
This works nicely to backup all of my important files, which I can
do much more frequently and easily than the full backup routine with
tar. What's more, I can also view the results of this file under mc.
This "hot_backup" routine created a tar/gzip file only about 132k in
size. My rule of thumb is that, when my important file backup exceeds
the size of a 1.44MB floppy disk, it's time to fully backup my system.
-
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 reply other threads:[~2002-12-09 7:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 7:00 Jerry James Haumberger [this message]
2002-12-09 10:32 ` tar for "full" floppy backup? dashielljt
-- strict thread matches above, loose matches on Subject: below --
2002-12-08 18:38 Jerry James Haumberger
2002-12-09 8:10 ` ichi
2002-12-08 21:07 ` dashielljt
2002-12-09 18:11 ` ichi
2002-12-09 10:16 ` dashielljt
2002-12-09 12:38 ` Mr. James W. Laferriere
2002-12-07 16:58 Mr. James W. Laferriere
2002-12-08 8:41 ` ichi
2002-12-07 20:03 ` Chuck Gelm
2002-12-08 2:10 ` whitnl73
2002-12-07 9:24 Jerry James Haumberger
2002-12-07 18:34 ` Chuck Gelm
2002-12-07 20:08 ` Rolf Edlund
2002-12-08 16:05 ` Ray Olszewski
2002-12-09 7:32 ` ichi
2002-12-11 18:12 ` Rolf Edlund
2002-12-08 8:36 ` ichi
2002-12-06 21:47 Jerry James Haumberger
2002-12-06 22:25 ` dashielljt
2002-12-06 22:26 ` dashielljt
2002-12-06 23:35 ` Chuck Gelm
2002-12-07 0:10 ` Ray Olszewski
2002-12-07 0:53 ` dashielljt
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=200212090658.XAA16146@cu.imt.net \
--to=jerryjh@imt.net \
--cc=linux-newbie@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