[prev in list] [next in list] [prev in thread] [next in thread] 

List:       veritas-bu
Subject:    [Veritas-bu] Steps to change Master Server Name
From:       "David McMullin" <David.McMullin () CBC-Companies ! com>
Date:       2010-02-23 17:28:16
Message-ID: C83D277D82594A4C8A269B151C83B89A01361FD405BE () CBCMAIL07 ! cbc ! local
[Download RAW message or body]

I have performed this rename on Solaris, but used the process mentioned below as a \
'cheat'

Production master name is foo, at ip address 1.1.1.1
Copy is bar, at 1.1.1.2

On bar - edit /etc/hosts and add entry for foo at 1.1.1.2 
Set DNS to use files first then DNS

On media servers, do the same!

When they try to connect to foo they will go to bar.

Edit the bp.conf on foo and remove any production systems, except foo and any media \
servers you have on that setup.


Basically fool the ip and network to references to foo go to bar.

You can also set the loop back address as the IP on bar, for foo, since the master \
server "talks to itself"...




Message: 3
Date: Mon, 22 Feb 2010 13:28:00 -0700
From: Jeff Cleverley <jeff.cleverley@avagotech.com>
Subject: Re: [Veritas-bu] Steps to change Master Server Name
To: VERITAS-BU@mailman.eng.auburn.edu
Message-ID:
	<5ec364e31002221228o1028c6cdo2b2196ea6943326a@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

I don't work with Solaris, but for purely a DR test purpose I would guess you could \
do it and actually have both systems on the network.

If you production server is named foo with an IP address of 1.1.1.1, you should be \
able to set up your new DR box at an unused IP address such as 1.1.1.2.  From there \
you set the local host file to your server name and IP, and either turn off dns or \
set it to use hosts first.

Any regular devices would still go to your production server unless you modify the \
clients also.  The DR server should not be getting the production server traffic \
since it has a different IP address.  This should allow you to bring up a DR server \
on the same network with the same host name.  I am not aware that the Veritas \
database uses the IP address also but I may be wrong.

If it were a real case of needing to put the DR server into production you would want \
to rename the server to the original name and IP address or change dns to point to \
the new IP address.

Jeff

On Mon, Feb 22, 2010 at 12:54 PM, Lightner, Jeff <jlightner@water.com>wrote:

> In a DR you'd typically set the name of the DR server to what the
> original master had been.   The only reason I could see for keeping
> original DR server name is that you intend to run whatever was already 
> on it concurrently with the NetBackup master you're about to load and 
> that would complicate your life incredibly.
> 
> -----Original Message-----
> From: veritas-bu-bounces@mailman.eng.auburn.edu
> [mailto:veritas-bu-bounces@mailman.eng.auburn.edu] On Behalf Of 
> lookn4me
> Sent: Monday, February 22, 2010 2:24 PM
> To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
> Subject: [Veritas-bu] Steps to change Master Server Name
> 
> 
> Yes you correct, I am looking to copy the catalog and its database to 
> the new host in order to test upgrading and locate break/fix issues 
> prior to the upgrade.  I need to have as much of the master server 
> functionality as possible.  The question I have is what needs to be 
> done in 5.1 MP4 version to change master server entries in the 
> associated databases?
> 
> Surprising this is an issue in Netbackup if one had to DR a box to a 
> different hostname, the inability to name the master something else.
> 
> 
> mdonaldson wrote:
> > Are you planning to copy your existing backup catalog (image 
> > database) over to the new environment?  If so, then the master 
> > server name is buried in that database it's a far-from-casual 
> > process to rename the master server.  There is no published process 
> > for it and Symantec will want to charge you for professional services to do this \
> > for you. 
> > If you're just going to create a new master server with it's own 
> > database, then it's simply a matter of building a new environment.
> > 
> > If you're going to do backups of one client to both environments,
> change
> > the first SERVER entry in the client's bp.conf file, that's the one
> that
> > should point to that client's master server.  It really should only 
> > matter, though, for client initiated actions, like restores.
> > 
> > A media server would be more complex, I'd suggest not trying to 
> > dual-master a media server.
> > 
> > -M
> > 
> > -----Original Message-----
> > From: veritas-bu-bounces < at > mailman.eng.auburn.edu 
> > [mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf 
> > Of
> lookn4me
> > Sent: Monday, February 22, 2010 6:37 AM
> > To: VERITAS-BU < at > MAILMAN.ENG.AUBURN.EDU
> > Subject: [Veritas-bu] Steps to change Master Server Name
> > 
> > 
> > I plan to replicate a production environment on a test server, but I 
> > need to change the master server name as the test environment will 
> > not be isolated.  Anyone out there have success with the process?  
> > The environment is Netbackup 5.1 MP4 on solaris 9 and 10 OS.
> > 

_______________________________________________
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[prev in list] [next in list] [prev in thread] [next in thread]