make_recovery or make_tape_recovery to remote tape

[Sudhakar_7]

Hi,

I have a sys1 and sys2 Both D Class servers running HP-UX 11.00
sys2 have tha DDS tape connected to it.And has an entry in .rhosts for sys1 and i am able to rlogin/remsh to sys2 with out any problem.

Now when i run sys1# make_tape_recovery -x inc_entire = vg00 -v -a sys2:/dev/rmt/0mn

i get the following error
sys2# make_tape_recovery -x inc_entire = vg00 -v -a sys1:/dev/rmt/0mn
* Creating local directories for configuration files and archive.

======= 03/08/03 00:26:43 MST Started make_tape_recovery. (Sat Mar 08
00:26:43 MST 2003)
@(#) Ignite-UX Revision B.3.3.116
@(#) net_recovery (opt) $Revision: 10.543 $

* Testing pax for needed patch
* Passed pax tests.
* Checking Versions of Ignite-UX filesets
ERROR: Failed to open tape device /dev/rmt/0mn:No such device or address
(errno = 6).
ERROR: Check tape device failed.

======= 03/08/03 00:26:49 MST make_tape_recovery completed unsuccessfully
sys2# make_recovery -ACv -d sys1:/dev/rmt/0mn
NOTE: make_recovery(103): The make_recovery command will be replaced by
make_tape_recovery. Both commands are supported in this
release (Ignite-UX Revision 3.2). Please read the man page
make_tape_recovery(1M) for usage of the new command. In a
future release, make_recovery will be replaced by a script
that calls make_tape_recovery.
Option -A specified. Entire Core Volume Group/disk will be backed up.
sys1:/dev/rmt/0mn: No such file or directory
make_recovery(280): Archive destination nile:/dev/rmt/0mn not found
make_recovery(210): Encountered a fatal error.
make_recovery(212): Please fix errors and re-try.


what to do now to create ignite backup on remote tape.

note that even make_recovery also not able to open remote tape

Regards

Sudhakar J

[Norman_21]

Hi,

Take alook at this forums. It has been discussed several times.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xfb6ffd3f91d3d5118ff40090279cd0f9,00.html

Thanks.

[Pete Randall]

The simple answer is that you can't do this remotely. You need a local drive or you need to do a make_net_recovery to an Ignite server instead.

Pete