Thanks to all who replied. I have received over 30 replies!
Forgive me to not to list the names who replied.
Here is my summary:
1) Sean Ward <wards@snk077.ast.lmco.com> pointed:
Subject: 10.1) My rdump is failing with a "Protocol botched" message.
What do I do?
The problem produces output like the following:
DUMP: Date of this level 0 dump: Wed Jan 6 08:50:01 1993
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/rsd0a (/) to /dev/nrst8 on host foo
DUMP: mapping (Pass I) [regular files]
DUMP: mapping (Pass II) [directories]
DUMP: estimated 8232 blocks (4.02MB) on 0.00 tape(s).
DUMP: Protocol to remote tape server botched (in rmtgets).
rdump: Lost connection to remote host.
DUMP: Bad return code from dump: 1
This occurs when something in .cshrc on the remote machine prints
something to stdout or stderr (eg. stty, echo). The rdump command
doesn't expect this, and chokes. Other commands which use the rsh
protocol (eg. rdist, rtar) may also be affected.
The way to get around this is to add the following line near the
beginning of .cshrc, before any command that might send something
to stdout or stderr:
if ( ! $?prompt ) exit
This causes .cshrc to exit when prompt isn't set, which distinguishes
between remote commands (eg. rdump, rsh) where these variables are not
set, and interactive sessions (eg. rlogin) where they are.
2) many people suggested the following which is exactly what I want:
ufsdump 0f - blah | rsh remotehost dd of=/dev/dsk/blah
rsh source_machine "ufsdump 0fs - 100000 /filesystem"|dd of=/my/disk/path
I like the second line, because I want to issue the backup command from the node
has the local backup disk.
3) the reason I choose to backup local disk to a remote raw disk instead of remote
"raw" tape is, sometimes it is more convenient.
Happy Holidays!
*--------------------------------------------------------------------------*
* Shouben Zhou | e-mail: zhou@pcs.cnu.edu *
* College of Business,Science & Technology| Phone : (757)-594-7749 *
* Christopher Newport University | Fax : (757)-594-7919 *
*--------------------------------------------------------------------------*
> From zshouben@PCS.CNU.EDU Tue Dec 16 03:19:25 1997
> Sender: sun-managers-relay@ra.mcs.anl.gov
> Date: Mon, 15 Dec 1997 13:53:18 -0500
> From: zshouben@PCS.CNU.EDU (Shouben Zhou)
> Reply-to: zshouben@PCS.CNU.EDU (Shouben Zhou)
> Followup-to: zshouben@PCS.CNU.EDU (Shouben Zhou)
> To: sun-managers@eecs.nwu.edu
> Subject: follow-up of backup the file system cross the network.
> X-Sun-Charset: US-ASCII
> Content-Length: 1660
>
> My first email may not be clear enough. Here is my problem to backup the file
> system:
>
> If I type:
>
> #ufsdump 0f remote:/dev/rmt/0h /dev/rdsk/c0t0ds0s
> it works, because "/dev/rmt/0h" is a remote tape drive.
>
> But if I type:
>
> #ufsdump 0f remote:/dev/rdsk/c0t2d0s0 /dev/rdsk/c0t0d0s0s,
>
> I got:
>
> DUMP: Writing 32 Kilobyte records
> DUMP: Date of this level 0 dump: Mon Dec 15 13:39:22 1997
> DUMP: Date of last level 0 dump: the epoch
> DUMP: Dumping /dev/rdsk/c0t0d0s0 (freedom:/) to courageous:/dev/rdsk/c0t2d0s5.
> DUMP: Mapping (Pass I) [regular files]
> DUMP: Mapping (Pass II) [directories]
> DUMP: Estimated 635908 blocks (310.50MB).
> DUMP: Protocol to remote tape server botched (in rmtgets).
> DUMP: Lost connection to remote host.
> DUMP: Bad return code from dump: 1
>
> Here I do want to use remote disk as a backup device instead of tape drive for
> easy maintenance.
>
> But If I type:
>
> #ufsdump 0f /dev/rdsk/c0t2d0s0 /dev/rdsk/c0t0d0s0
> it works. Now "/dev/rdsk/c0t2d0s0" is a LOCAL disk.
>
>
>
> > ufsdump is a good utility we use here to back filesystems to either local
> > or remote tape drives, but it does not support to backup to the remote disks,
> > say remote_node:/dev/rdsk/c0t2d0s0.
> >
>
> > Does anybody know how to backup the local disk file system to a remote disk?
>
> *--------------------------------------------------------------------------*
> * Shouben Zhou | e-mail: zhou@pcs.cnu.edu *
> * College of Business,Science & Technology| Phone : (757)-594-7749 *
> * Christopher Newport University | Fax : (757)-594-7919 *
> *--------------------------------------------------------------------------*
>
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:11 CDT