| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 9969.1 | | finder.uvo.dec.com::COFFEYJ | La Feline Flooz - a unix cat | Wed May 28 1997 12:01 | 5 |
| I think the answer is you can have a vdump or an rdump
but you can't remotely do a vdump. I can't remember/
never knew the reason why but here we always recommend
NSR as the answer to remote backup of an Advfs file
system.
|
| 9969.2 | | NABETH::alan | Dr. File System's Home for Wayward Inodes. | Wed May 28 1997 13:33 | 14 |
| The way you do remote dumps with vdump is to write to stdout
and pipe that an rsh which runs dd(1) on the remote system
just as the example command shows. The problem is likely
one of data block sizes. vdump (as I recollect) likes to
write with a 60 KB block size. I expect that vrestore also
expects a 60 KB block size. Going across the pipe will
change the block size and without an explicit size, who
knows that dd(1) will use. I think all you need to do is
specify an obs= on the dd(1) size and probably an ibs=
on the restore side.
I'd aim at getting the vdump to be readable on a local
tape drive and then figure out what block size arguments
to pass on the rsh dd | vrestore for a remote vrestore.
|
| 9969.3 | more info | DECWET::DADDAMIO | Design Twice, Code Once | Mon Jun 02 1997 16:49 | 10 |
| > To restore, from system A
> rsh <remote node B> dd if=/dev/rmt0h | /sbin/vrestore -xf -
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This need to be "rsh <remote node B> dd if=/dev/rmt0h obs=60k". The
last reply was correct about the block size changing when doing the
pipe.
Also as of Steel we will have rvdump and rvrestore which will recognize
remote devices (they will work like rdump and rrestore).
|