> 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.

Does the size of the backup appear correct for the size of the raw
devices?

> 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.

Odd.  

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

By specifying a saveset, you don't need -c client.  (only one client is
on the saveset, so the option is redundant).

-- 
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

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