Many many thanks to all who contributed
Keyword here seems to be 64k.
This worked perfectly (verified over & over)
Backup:
xxx#vdump -0 -f - /|rsh yyy dd of=/dev/dat bs=64k
Verifying:
xxx# rsh yyy dd if=/dev/dat bs=64k| vrestore -f - -t
On Tue, 12 Dec 2000, Tru64 User wrote:
> More information on vrestore problem:
> I am running OSF4.0F on both machines, local and
> remote. the tape device refered here, /dev/dat, is a
> character device. I was given a line to try:
> xxx_at_vdump -uCf - / |rsh yyy "dd bs=60k of=/dev/dat"
> No luck either
> Getting:
> vdump: Status at Tue Dec 12 10:22:20 2000
> vdump: Dumped 76 of 76 bytes; 100.0% completed
> vdump: Dumped 170 of 170 directories; 100.0%
> completed
> vdump: Dumped 13 of 13 files; 100.0% completed
> vdump: Dump completed at Tue Dec 12 10:22:20 2000
> 0+113 records in
> 3+1 records out
> And restore shows:
> xxx_at_rsh yyy dd if=/dev/dat bs=60k | vrestore -t -f -
> 0+0 records in
> 0+0 records out
> vrestore: unable to use save-set; invalid or corrupt
> format
> which looks more weird. So far I doing my backups
via
> nfs mounts,
> would like to move to vdump/vrestore remotely if
able
> to do so.
> Anymore suggestions, ideas are welcome.
>
>
> > Hi Admins, I know this topic has been discussed
> > before, but still I could not explain to myself
what
> > is wrong here.
> > COMMAND AT LOCAL MACHINE <xxx> WITH OUTPUT:
> > xxx_at_/sbin/vdump -b 60k -0 -uvf - / |rsh yyy dd \
> > of=/dev/dat obs=60k
> > vdump: Status at Mon Dec 11 14:13:59 2000
> > vdump: Dumped 63998642 of 63998642 bytes; 100.0%
> > completed
> > vdump: Dumped 170 of 170 directories; 100.0%
> > completed
> > vdump: Dumped 1495 of 1495 files; 100.0%
completed
> > vdump: Dump completed at Mon Dec 11 14:13:59 2000
> > 85360+42370 records in
> > 1012+0 records out
> > xxx_at_/usr/users/mollel$
> >
> > (Shows success of vdump, right?)
> >
> > VERIFY FROm LOCAL MACHINE:
> >
> > xxx_at_/usr/users/mollel$ rsh yyy dd if=/dev/dat
bs=60k
> \
> > | vrestore -t -f - (Also tried without -f)
> > dd read error: No space left on device
> > 0+0 records in
> > 0+0 records out
> > vrestore: unable to use save-set; invalid or
corrupt
> > format
> >
> >
> > ************* PROGRAM ABORT **************
> >
> > vrestore: can't obtain fileset attributes
> >
> >
> > xxx_at_/usr/users/mollel$
> >
> > (THIS IS 4MM TAPE, WITH CAPACITY OF 4GB. I BACKED
UP
> > ONLY ROOT FILESYSTEM, which uses only
> > 61701(1024k blocks), so why should it say no space
> on
> > device. Please help explain)
> >
> > (THEN WENT TO MACHINE yyy WHICH HAS THE TAPE
DEVICE)
> >
> > yyy_at_/usr1/users/mollel$ mt -f /dev/dat rew
> > yyy_at_/usr1/users/mollel$ vrestore -t -f /dev/dat
> > obs=60k
> > vrestore: Date of the vdump save-set: Mon Dec 11
> > 12:30:36 2000
> > vrestore: unable to read from device '/dev/dat';
> > incomplete read 512 < 65536
> > vrestore: unable to restore block <1>; corrupt
block
> > Memory fault(coredump)
> > yyy_at_/usr1/users/mollel$
> >
=====
Richard F. Mollel
Systems Administrator
SAIC
Greenbelt, MD
Experience is what allows you to recognize
a mistake the second time you make it.
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
Received on Wed Dec 13 2000 - 22:39:24 NZDT