From: Liang, Warren (Warren.Liang@sms-ito.com)
Date: Wed Jul 09 2003 - 13:42:25 EDT
Morning:
Thanks to Alan Rollow's recommendations, I am able to rebuild the O/S.
The commends to created the backup tape were:
vdump -0 -N -u -v -f /dev/rmt0h /
vdump -0 -N -u -v -f /dev/rmt0h /usr
...
vdump -0 -u -v -f /dev/rmt0h /usr/users123
Media type: DLT Type III + Compress
Tape device: TZ88
I changed the commend to:
vdump -0 -u -v -f /dev/nrmt0h /
vdump -0 -u -v -f /dev/nrmt0h /usr
...
vdump -0 -u -v -f /dev/rmt0h /usr/users123
The rebuilding process works fine with regardless of tape type III or IV.
Here is Alan Rollow's reply:
There shouldn't be any difference due to the tape, assuming
the relevant drives are working correctly. I don't recall
enough of the details on how you made the original backups,
but I'll offer some general comments:
1. If the original file system is UFS, make the backup
with dump instead of vdump. For the cleanest backup
you'll want to shutdown to single user and unmount
whatever file systems you can.
2. Keep the backup simple. Rather than using an option
to say, "use the norewind tape device", use the -f
option and specify the norewind tape device. If the
tape hardware supports compression, don't have the
software also try to compress the data.
3. It is easy to make mistakes trying to put multiple
backups on a single tape. When in doubt, use one
tape for each file system.
4. Given the differences in the two systems, consider
whether it would be easier to install a fresh
Tru64 UNIX on the DECpc and then restore the
application once that is stable.
5. If you have doubts that the data is getting to the
target system intact, have doubts and check it.
Create a large file of known content (or use an
existing file). Back it up to each tape and drive
type at issue, then restore it elsewhere. Use
cksum on the original and restored backup copy to
verify that they seem the same. If on the same
system, compare them (cmp -s).
My original post:
I am perform a Tru64 V4.0E rebuild/restore. The media is DLT III tape; tape
drive is TZ88. Target disk is rz0. Commands used to backup / (root) and /usr
file systems are:
vdump -0 -N -u -v -f /dev/rmt0h /
vdump -0 -N -u -v -f /dev/rmt0h /usr
...
While performing the O/S rebuild (which includes root and /usr file systems
only), problem occurs. Following are my procedures:
1. Boot from Digital UNIX V4.0E Operating System CDROM # boot mka400
2. # cd /dev and # MAKEDEV rz0 tz6
3. # disklabel -z rz0; disklabel -rw rz0; # newfs /dev/rz0a and # newfs
/dev/rz0g
4. # mount /dev/rz0a /mnt
5. # cd /mnt and # vrestore xvf /dev/nrmt0h
6. # cd /mnt/dev and # MAKEDEV rz0
7. Modify /mnt/etc/fstab to change root and /usr's mount points to rz0a
and rz0g respectively.
8. Unmount /dev/rz0a, mount /dev/rz0g, and complete restore /usr from
tape.
9. Shutdown
10. >>> boot dka0 -fi "genvmunix"
...
Mounting local filesystems
/dev/rz0a on / type ufs (rw)
/dev/rz0g on /usr type ufs (rw)
initsh: /sbin/init.d/autosysconfig: not found
Apr 13 14:57:00 update: started
The system is coming up. Please wait...
The system is ready
Digital UNIX Version P4.0 (Amnesiac) console
Login: root
Digital UNIX Version P4.0 (Amnesiac) console
Login:
The "password:" never shows up.
My first reaction was "a bad tape". I have tried 4 different DLT III tapes,
all failed.
However, I used a DLT Type IV tape to backup root and /usr file systems, by
using the same vdump commands, following the same rebuild/restore
procedures, system starts up successfully.
Is there any restriction or compatibility issue between DLT III and IV
tapes?
> Warren Liang
> Systems Administrator
> Systems Management Specialists
> (714) 986-8342
> **************************************************************************
> ******
> NOTICE: This Email (including any attachments) may contain confidential
> and privileged material for the sole use of the intended recipient(s). Any
> review, use, copying, distribution or disclosure by others is strictly
> prohibited. If you are not the intended recipient (or authorized to
> receive for the recipient), please contact the sender by reply email and
> delete all copies of this message including any attachments. Thank you.
>
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:26 EDT