Video Screencast Help

Restore on MS cluster failing with 'invalid server (37)'

Created: 27 Mar 2009 • Updated: 24 May 2010 | 4 comments


I read about same issues with MS Exchange cluster and I think I might have the same problem, can anyone confirm?

Netbackup 6.5.3
MS cluster windows 2003

I can access the backup listing from the cluster node console (sdcnat0-000013) from which the backups are iniated.  This node name dynamically points to the active node of the physical cluster (either sdcnat0-000009 or sdcnat0-000010). I can browse and choose files to restore. I launch the restore and then it freezes up for about 2 minutes and get the invalid server (37) message.
I have the altnames set up.

Anyone have an idea??

Comments 4 CommentsJump to latest comment

davidbe's picture

Ok, I did some more testing, if I initiate the restore from another client console (any other server), I can perform the restore, now how weird is this???

J.H Is gone's picture

Read/heard somewhere that you cannot do an exchange restore from the BAR on the Exchange server, do it form the master, the media, or a remote admin console and it will work fine.

don't know where I got that from but I know it is something that has stuck in my head.

I don't have to know how to spell....I work on Unix.
NetBackup 7.0.1 - AIX & Windows

davidbe's picture

Yes, thats exactly what settled the issue temporarily, but it is not a permanent solution for us, the clients must be able to do restores directly from the cluster.  Anyway, thats plainly a step back cause we had those clusters with 6.0MP5 and could launch restores from the cluster node. So what they did in 6.5.3, I really don,t know but there must be a permanent solution.