Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Running Two Netbackup Environment (Two Master Servers) With The Same Hostname In The Same Domain

Created: 20 Mar 2013 | 8 comments

We have a netbackup 7.0.1 environment VCS (two nodes) Global Cluster Option and one node in DR for netbackup catalogue replication.

We recently built a new netbackup 7.5.0.5 environment VCS (two nodes) Global Cluster Option and one node in DR for netbackup catalogue replication

with the same hostname and IP address of the old 7.0.1 environment and unplumb the publich IP interface to the 7.0.1 env so that it would not be reached on the domain/network.We did not copy/migrate the catlogue of the 7.0.1 env to the 7.5.0.5 env and we are currently running our production on the 7.5.0.5 environment pefectly.

We need to bring up the 7.0.1 env so that we can get information to the media used there ,and import them onto the 7.5.0.5 env,run a restore from 7.0.1 if it is need from the previous backup and have been battling/struggling with this.

Our environment has a DNS and the hostname is reference on DNS to a particular IP already for the 7.5.0.5 ,so bringing up the second 7.0.1 env with  the same hostname and IP/diferent IP will conflict DNS.

Could anyone int he house assist with CLUES of getting the7.0.1 env running simultaneosuly with the current prodcution 7.5.0.5 env.

Your information is highly appreciated and thanks a million in advance.

Our environment has Oracle RMAN ,VMware,Mysql as well as window/UNIX OS

Comments 8 CommentsJump to latest comment

Mark_Solutions's picture

The only way i can think of doing this is to isolate them first, bring them up, give them new IP addresses and add hosts file entries to all nodes with the Master node and virtual names all pointing to the new IP addresses

You should then be able to put it on the network

Not sure how it will actually like coming up and getting onto the domain though!

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Marianne's picture

What is your Master server OS? This is quite easy on Unix/Linux servers - Just change IP addresses (including virtual) on old master nodes and keep same hostnames (including virtual hostname).

As long as this IP does not exist in DNS, you will be able to access the old master and bring NBU online.
New IP's must only exists in local hosts files and VCS config.

Just ensure that policies are all disabled and nbpem is stopped/disabled on 7.0.1 installation.

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

Ayes's picture

The master servers both old (7.0.1) and new (7.5.0.5) is Solaris 10 OS.

OLD MASTER ----------down currently

-virtual name is nbu1—10.1.230.162

-nodes are ojnbu1—10.1.230.160 and ojnbu2—10.1.230.161 with DR single node cluster iknbu3—10.1.105.95

NEW MASTER ----------running currently

-virtual name is nbu1—10.1.230.162

-nodes are ojnbu1—10.1.230.160 and ojnbu2—10.1.230.161 with DR single node cluster iknbu3—10.1.105.95

We want to get the old 7.0.1 environment running simultaneously with the new 7.5.0.5.

This is because we need to have information from the catalogue about status of media tape media expiration on the old catalogue, which media has  which data as restore request are being made in the old 7.0.1 environment. We have Infinity,1 year ,6 months as well as 1 month retention policy in the old environment and these are critical data.

Your contribution so far is very much appreciated.

Regards.

Ayes.

Mark_Solutions's picture

As i mentioned earlier I would try using hosts files on every node - you need to change all of the "old" IP addresses and then on every node add an entry for their names and the virtual name against the new IP addresses

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Ayes's picture

Thanks a  million times Mark and Marianne.I am indeed very grateful for your inspirations especially to the younger generation on symantec productus.I will implement this and provie feedback.

BR,

Ayes.

Lagos Nigeria

Ayes's picture

Hello House,

I have implemented the clues suggested and cannot bring netbackup on line:

-Change IP address of nodes

-Update /etc/hosts filess on all node

-Updated /etc/VRTSvcs/conf/config/main.cf  witht he new IP

-Ensure the new IP is not referencecd on DNS

I am verymuch grateful for the efforts so far from the house

Is ther any other clue to bring this envir up and running again

BR

Marianne's picture

.... cannot bring netbackup on line.....

What exactly is not coming online?

Please do the following:

Bring all resources online up to IP and mount (only NBU resource offline).
Mark NBU resource as non-critical (to prevent failover attempt.
Create bpdbm and bprd log folders on active node.
Verify that PBX is running (should not be a cluster resource and always running).
Start NBU (netbackup start)

Let us know what happens - any error messages?
Which daemons processes get started and which ones don't? (post output of bpps -x)

Logs required will depend on answers to above questions.

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