Video Screencast Help

renaming Master server

Created: 21 Aug 2009 • Updated: 22 May 2010 | 6 comments

I have a Netbackup running on 6.0 MP7 and the O/S is Solaris 9 and It is a Master/Media server plus I also have 17 media servers . Now we are going to upgrade the master from  NetBackup 6.0 MP7 to NetBackup 6.5 MP4 and also OS upgrade from Solaris 9 to Solaris10. While we move from solaris 9 to solaris 10 we will rename the master server and new master server is going to be just Master and emmserver only.

I have 1000 plus media belong to old master becuase it was also media server before. Now after the upgrade the old master will be rejoin back to new master as media server without host rename. The question that I have is whats the best way to deal with this kind of situation,

I want to know how to proceed , what are the steps to be taken
I really need your valuable inputs specially from experts like Stumpr,Deepak W, J.Hinchcliffe, Marianne van ,den quebek and yasuhisa Itoh and also others please

Thanks
Steve

Comments 6 CommentsJump to latest comment

Anton Panyushkin's picture

Here's the technote.http://seer.entsupport.symantec.com/docs/267137.htm
Consult Symantec prior to making any changes.

Mouse's picture

However, we have completed four migration projects within last year with renaming of master server in the task list.
Usually move from one version of Solaris to another isn't really big deal, but renaming is (if I understand you correctly, you just want to move EMM and catalog database to a new server with new name).
I would recommend to leave the Master server name as it is with it's role. Just assign all of the storage units currently belongs to master to the new media server. This is free and fully supported way (you can even migrate from one physical machine to another by backup/recovery technique but you have to preserve the hostname) - otherwise you have to engage Symantec Consulting (as Anthony said above) and pay them money. But if you just want to split the role of master server and change the hostname I doubt if it really price wise

Rakesh Khandelwal's picture

Renaming master server isn't easy thing to do and Symantec Technical Support does not support it. However, Symantec Professional Services would be more than happy to assist you. Changing the master server name means manually updating the catalog, which is very risky.

If there isn't any pressing reason, install  new server with Solaris 10 and use hostname same as the old master server. This way your upgrade is straight forward. I can't think of any reason for changing the master server name unless you work for NetApp and your master server name is Hitachi or EMC :)

Once you cutover to new H/w with new OS but with existing master server name, add the old master server as media server but with different name.

Nicolai's picture

You have 1000+ client pointing to the old master server name, I would keep the old master server name. Possible making it a virtual name by using :

REQUIRED_INTERFACE = {IP to use}

in both vm.conf and bp.conf (requires more IP per NIC or two NIC's). This way host A and act as master server using name B. This also  requires you rename the old master server when it re-join the Netbackup domain.

Good luck with the project.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Mouse's picture

Having REQUIRED_INTERFACE set to ip adress can lead to complete catalog loss during the upgrade, as we faced month ago or inability to cleanup image directory (http://seer.entsupport.symantec.com/docs/314318.htm).

You have always set this property to hostname not the ip address

Nicolai's picture

You need to decommision the media server part of the master server before going down the path I suggested

What is the process for decommissioning a NetBackup 6.0 media server 

Thanks Mouse for the "heads up".

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.