Video Screencast Help

Tech-refreshing master server from Solaris to Linux: same IP address?

Created: 07 Feb 2014 • Updated: 20 Feb 2014 | 4 comments
This issue has been solved. See solution.

Hello,

We are  looking to tech-refresh Solaris 10 Master server to Linux.

I'm looking at this TechNote and I belive it's something we can do with full catalog backup and restore:

Using catalog backup and recovery to transfer NetBackup catalogs between UNIX or Linux master servers as part of a hardware refresh

http://www.symantec.com/business/support/index?pag...

Prepare the new master server using the same host name and IP address as the old master server (ensure that the conditions stated above are met)

Why is "same IP address" part is important? Is it recorded anywhere in the database?

If we can update DNS and point the same hostname to a new IP address and then clean host cache on all media servers with "bpclntcmd -clear_host_cache" - would that work?

Please advise.

Thank you!

Operating Systems:

Comments 4 CommentsJump to latest comment

SymTerry's picture

Hello,

TECH77448 does say that you need both the IP address and Name. I spoke with a backline tech on why that would be in there and was told its most likley so a network admin would not have to deal with clearing the host cache. 

You are correct though, clean host cache on all media servers an you should be fine.

SOLUTION
revaroo's picture

I don't see the need for same IP address, I've had customers change the IP of the Master loads of times. Yes, you sometimes have to clear the host cache as you mentioned.

Linette V's picture

Along with the host cache mentioned above, a change of IP address can be an issue if any tuning or modification has been made to your installation.

For example if the setting REQUIRED_INTERFACE or PREFERRED_NETWORK has been used in the bp.conf (on the master or any NetBackup machine that interacts with it) and set to an IP address.

http://www.symantec.com/docs/HOWTO60779

If these settings are in place then after migration you would risk failures.  If they are not being used you should be fine (as long as forward and reverse lookup are all well configured).

Marianne's picture

I have personally migrated a master from Solaris to Linux with new IP on new Linux master. 

No issues.

As long as you are mindful of possible hosts entries on media servers and clients that need to be updated, there is no configuration database inside NBU where IP address is recorded.
Host cache is the only place where NBU 'hangs on' to IP address for an hour.
In all honesty - a change like this hardly ever takes less than an hour (during which all processes on media servers should in any case be stopped)! Which makes host cache almost a none-issue....

All that remains then is REQUIRED_INTERFACE or PREFERRED_NETWORK...

Good luck! Let us know how it goes!

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links