Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Moving UNIX clients to new Windows NBU 7.0 Master Server

Updated: 12 Nov 2010 | 2 comments
rsamora@eprod.com's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Windows NBU 6.5.5 Master, HP-UX 11.31 clients and Linux 2.5.21 clients.  I want to retire the Windows NBU 6.5.5 server and move the clients to a new Windows NBU 7.0 Master server.  The Windows clients moved over with no problem.  I couldn't bring up the UNIX client properties from the NEW server so I went to the OLD server, brought up the client properties page, and changed the Master server for each UNIX client from OLD to NEW.  I still cannot pull up the UNIX client properties from the NEW server.  When I try to backup a client I get Status 24, socket write failed.  All of the clients, Windows and UNIX are still running either NetBackup 6.5 or 6.5.5 client.  Is there something else I need to do on the UNIX clients to make them see the new Master server?  I'm not a UNIX guy but I don't even know what to ask my UNIX guy so I would appreciate any help.

Thanks,
Randy

Comments

J.Hinchcliffe's picture
11
Oct
2010
0 Votes 0
Login to vote

check

Check to see if the unix admins had put the master and media server names in the /etc/hosts file ( instead of using DNS).

They may need to add the new master name to the host file.

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

rsamora@eprod.com's picture
11
Oct
2010
0 Votes 0
Login to vote

Reverse Lookup

You pointed me in the right direction.  I couldn't do a reverse lookup from the clients back to the new master.  I resolved that issue and all is well. 

I've always found that if there's a network issue between two servers, NetBackup will find it.

Thank you J.