[comp.unix.ultrix] rdump - lost connection

gfl@tuhold.UUCP (Gerhard Fleischanderl) (12/23/88)

Reply-to: gfl@tuhold.UUCP (Gerhard Fleischanderl)


I have serious problems with rdump(8):

We are running a VAX-11/750 under Ultrix 1.0 and a MicroVAX-II
under Ultrix 2.0, both connected via Ethernet.
(Nice mixture of releases, isn't it?)

Trying an rdump from the MicroVax to the tape (rmt8) at
the VAX-11/750 results in the error message
	Lost connection to remote host.

It's interesting to see that the command rdump actually
does work from the VAX-11/750 to the MicroVAX"!!!

Trying an rrestore yields the same results.
The files /etc/rdump, /etc/rrestore, and /etc/rmt exist
on both machines.

Who can tell me what has gone wrong?
If it's just the different releases of Ultrix: We are
going to bring updates to both machines.

If anyone has the solution for my rdump-problem,
please let me know.
Thanks.

Gerhard Fleischanderl
Databases and Expert Systems Subdivision, Technical University Vienna
Paniglgasse 16,  A-1040 Vienna, Austria
e-mail (UUCP): ...!mcvax!tuvie!tuhold!gfl

avolio@decuac.dec.com (Frederick M. Avolio) (12/31/88)

Reply-to: avolio@decuac.dec.com (Frederick M. Avolio)


Regarding rdumps between two different version of ULTRIX.  I am very sure that
the versions you mention are not compatible.  That is to say, 
2.0 can recognize an old format but 1.0 cannot recognize a new one.

Fred

bin@primate.wisc.edu (Brain in Neutral) (12/31/88)

Reply-to: bin@primate.wisc.edu (Brain in Neutral)


[original article references "lost connection" in rdump/rrestore
between two Ultrix machines using different versions of Ultrix]

I experienced the same problem using rdump/rrestore with a 2.2 VAXstation
using the tape drive on a 1.2 VAX 8200.

Using the o option fixes the problem.  This is in the man pages.
(Maybe Ultrix 2.0 rdump/rrestore don't have an o option?).

I probably wouldn't have known to try this except that after losing
the connection, both rdump and rrestore suggested to use o!!

Paul DuBois
dubois@primate.wisc.edu	rhesus!dubois
bin@primate.wisc.edu	rhesus!bin

collins@sleepy.unm.edu (William Collins) (12/31/88)

Reply-to: collins@sleepy.unm.edu (William Collins)


In article <75675@felix.UUCP> gfl@tuhold.UUCP (Gerhard Fleischanderl) writes:
>Reply-to: gfl@tuhold.UUCP (Gerhard Fleischanderl)
>
>
>I have serious problems with rdump(8):
not quite...
>We are running a VAX-11/750 under Ultrix 1.0 and a MicroVAX-II
				   ^^^^^^^^^^
>under Ultrix 2.0, both connected via Ethernet.
       ^^^^^^^^^^
>(Nice mixture of releases, isn't it?)
yeah, *real* nice.

>Who can tell me what has gone wrong?
rmt(8) is not real friendly when it gets a command that it doesn't understand.
2.0 has some special commands for rmt(8).  read rmt(8) and you will find:
     Any other command causes rmt to exit.

>If it's just the different releases of Ultrix: We are
>going to bring updates to both machines.
Good, that should "fix" it.

					Bill
					collins@unmvax.unm.edu
			Bill Collins
			collins@unmvax.unm.edu
			ucbvax!unmvax!collins

mangler@csvax.caltech.edu (Don Speck) (01/31/89)

Reply-to: mangler@csvax.caltech.edu (Don Speck)

Recent versions of Ultrix rdump use some nonstandard (and nonportable)
extensions which old /etc/rmt's (or those on machines with a different
byte order or word size) cannot understand.  /etc/rmt exits on errors.

To be fair, the original /etc/rmt had a nonportable command ('S'), but
at least nothing used it.  It ought to be removed.