In the Backup, Archive, and Restore on the client, go to File-> Specify
NetBackup Machines and Policy Type and make sure media and master server
is in that list.  I think I had a similar problem once and I believe
this is how I fixed it. All the servers have to be in the list although
only the master server should be marked as current.

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Charles
Ballowe
Sent: Tuesday, October 11, 2005 2:43 PM
To: Veritas List
Subject: [Veritas-bu] Re: error 37

I'm still stuck on this one.

It's showing up in the activity monitor log as a different box, grep'ing
the logs for that box name shows NOTHING (box was retired -- not even
the same IP). bprd logs on the master show that it is contacted from the
correct name doesn't even mention the name of the retired server.
Nothing about it in bperror.

I had created an altnames file to allow this one to browse the old
client last week sometime and it never worked. I've deleted that file
- does something need bouncing?

I can do a restore if i kick it off from the master server, but not
request it from the client.

-Charlie

On 10/10/05, Charles Ballowe <cballowe AT gmail DOT com> wrote:
> I have a client that is requesting a restore (files backed up by it, 
> restoring to it -- no alternate system involved) and is getting a 
> statuscode 37. This seems to be related to a server directed restore 
> from an invalid server - any reason why I might be seeing it on a 
> client/any clue as to resolution?
>
> -Charlie
>

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu