1) Use tprobe; Find via Archie; can ftp from internet host archives including:
18.104.22.168 ftp.uu.net /usenet/comp.sources.3b1/volume02
22.214.171.124 archive.cis.ohio-state.edu /pub/comp.sources.3b1/volume02
2) Use copytape; Find via Archie; can ftp from internet host archives including:
126.96.36.199 ftp.uu.net /usenet/comp.sources.unix/volume10
188.8.131.52 ccb.ucsf.edu /Comp.sources.unix/Volume10
184.108.40.206 cs.dal.ca /pub/comp.sys.sun/volume10
3) Use tcopy; % man tcopy (1)
4) Use "our tape duplication process shell script" or "my C program".
5) Use dd with the following options, et. al.; Or don't/why make copies at all.
> dd if=/dev/nrst0 of=/dev/nrst1 bs=126b
> Of course, this would need to be in a loop to process all the dump file
> son the tape. The block size should be the same as used for the dump
> command, 126 blocks (63k) is typical and the recommended value.
> You definitely _do_not_want_ conv=sync as this will pad blocks, ie add
> extra bytes into the file(s). You shouldn't need any conv options. Also
> Don't do conv=noerr, because that will ignore read errors in the copy.
> Also, you should add obs=blocksize.
> Why would you make copies in the first place? The mechanism I use is
> much easier:
> - Once a week, I made a complete backup set that would allow me to rebuild
> from scratch if it ever becomes neccessary
> (colleagues needed those some weeks ago because a strike would not allow
> anyone on the place their computers were and they had to move to another
> spot. So, backups are a good idea)
> - The fresh newest backup set remains on-site that week for uncareful users;
> - The next older one goes to the off-site spot.
> - NEXT DAY, the older-older set comes back from that spot (so there is
> *always* at least one copy off-site)
> - Then copies wait a few weeks until they are re-cycled. After a few cycles,
> they are archived. I have one archive copy per month.
> That is a much better approach, IMHO. Much less work.
THANKS TO: FOR REFERENCE TO:
Nico Garcia <firstname.lastname@example.org> tprobe
Phil Blanchfield <email@example.com> copytape
Koper Zangocyan <firstname.lastname@example.org> copytape
Mike Raffety <email@example.com> tcopy (1)
Henry Katz <firstname.lastname@example.org> tcopy (1)
Andy Toy <email@example.com> tcopy (1)
Steve Vu <firstname.lastname@example.org> tcopy (1)
John P. Linderman <email@example.com> tcopy (1),et.al.
Javier Santos <firstname.lastname@example.org> own sh script
Piete Brooks <Piete.Brooks@cl.cam.ac.uk> own C program
Glenn Satchell <glenn%ups.uucp@fourx.Aus.Sun.COM> dd (1), et. al.
Geert Jan de Groot <email@example.com> dd (1),mechanism
--- Forwarded mail from firstname.lastname@example.org (Rex Espiritu)
>From espiritu Mon Mar 29 14:46:37 1993
>From email@example.com Tue Mar 30 03:56:15 1993
>From: firstname.lastname@example.org (Rex Espiritu)
Reply-To: email@example.com (Rex Espiritu)
To: Sun Managers Mailing List <firstname.lastname@example.org>
Subject: WANTED: dd command to duplicate 8mm dump tape(s)
Cc: Rex Espiritu <email@example.com>
I'd like to make duplicate copies of 8mm dump tapes to keep the month end
backups on-site as well as archived off-site. If anyone else does this on
a regular basis, I'd appreciate your sending me the exact dd command(s)
you use for comparison. I'm particularly interested if any "conv" option
is desirable to use, e.g.:
# dd if=/dev/nrst0 of=/dev/nrst1 conv=noerror,sync
Thanks in advance,
-- M. Rex Espiritu, Jr. Carnegie Group, Inc. firstname.lastname@example.org 5 PPG Place Voice: 412 642-6900 x233 FAX: -6906 Pittsburgh, PA 15222
--- End of forwarded message from email@example.com (Rex Espiritu)
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:07:44 CDT