Hi All.

I have a question on  the RAWASM directive.  Have checked through the
archives and not found anyone withthe same problem.

OS = HPUX
NW version 7.3.2 (windows networker server, both clients  HPUX)
To back the data up, we created a directive  and added the following
information to it (have cut most of the lines out)
<< /dev/vgbcv12 >>
+rawasm: rp012sys01
+rawasm: rp012temp01
+rawasm: rp012undo01

Then created a client (SUP) and assigned the directive to it and put in the
saveset field
/dev/vgbcv12/rp012sys01
/dev/vgbcv12/rp012undo01
/dev/vgbcv12/rp012temp01

We also added the DEV machine to the client configuration of SUP to allow
DEV to restore data from SUP.

This then seems to backup ok with no errors.
We then go to the second host (DEV) and create the symbolic links for
/dev/vgbcv12 pointing to the correct device group (vgbcv25).
We then starrt recover (recover -c SUP) and select one of the files (have
also tried all three).
NetWorker then requests tapes and restores 4KB worth of data (I believe this
is the directory tree).  We have also tried a re-directed recover to point
to the vgbcv25 volume group with no success.

We also cannot use the "-S ssid" option as according to the man page it is
incompatible with the "-c client"

Nothing is logged in the deamon.log or messages files on either of the
clients or the NetWorker server.  It doesn't give any errors on STDOUT.
Recover gives no response apart from mounting the volumes and restoring the
4KB worth of data

Maybe I'm missing something obvious.  Is anyone able to give me a hint as to
where to start looking next?

Cheers!
Brendan Sandes

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER