We changed the master server's name twice.......minor problems.
Be sure to do a fresh database backup of the NetBackup configuration
and catalogs.  After renaming the master server or after setting
up a completely new server, which is what we did twice, use
bprecover with the "-host <new name>" option.  This will do the
appropriate mapping to the new name.  However, there is still
one adjustment that must be made outside the GUI.  I believe we
used the /usr/openv/volmgr/bin/tpconfig command to set the
Volume Database Host.  It is good practice to check that everything
is configured properly when finished.

Leo R. Labonte
AT&T
(732) 420-6080
llabonte AT att DOT com


-----Original Message-----
From: SIBLEY, Ken R. - ACCOREL [mailto:sibley_ken AT accorel DOT com]
Sent: Wednesday, February 06, 2002 5:09 PM
To: 'NetBackup List'
Subject: RE: [Veritas-bu] Moving a backup/media server to a new platform


> Subject: RE: [Veritas-bu] Moving a backup/media server to a 
> new platform
> 
> 
> STOP!!    WAIT!!
> 
> I would advise keeping your current hostname.  It is a 
> nightmare to change it.

I want to second this.  We done this both ways.  The first
time we did not know better and changed hostnames.  This was
2 years ago and found out the hard way that it is not supported
by Veritas support.  They tell you to hire their professional
services people to perform the move.

About six months ago we changed servers and took the hostname
with us and the biggest issue we had was moving the tape
library and getting it configured correctly.  All done during
on 9 hour period of time on a Saturday afternoon.

Make sure you do as much research as possible and have as
detailed a plan as possible. It can make a world of difference.

Good Luck,
Ken Sibley
Sr. Unix Admin
Accor Economy Lodging
ksibley AT accorel DOT com

> Also,  if you change it, all of the clients' bp.conf file 
> will have to change.  It is just
> creates a huge mess.  
> 
> If you retain the host name, you can tar over all of your 
> backup images/catalogues, 
> (and your entire /usr/openv/ directory) configure your robot 
> as a new device, test it,
> and your back up and running in a day.  I just upgraded from 
> an Sun E3000 to and Sun E450
> with a T300 Disk Array using this scenario and had no 
> problems.  It takes a lot of planning, but it is
> well worth it.  We only had about six hours of downtime and 
> most of the time was spent moving
> the data.  Let me know if you want more info on this.
> 
> Hope this helps.
> 
> Gina Robinson
> UNIX System Administrator
> TRW E-Enterprise
> 
> -----Original Message-----
> From: Jeffrey Dykzeul [mailto:Jeffrey_Dykzeul AT west.raytheon DOT com]
> Sent: Wednesday, February 06, 2002 12:59 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] Moving a backup/media server to a new platform
> 
> 
> Current backup/media server platform:
> 
>      Sun SPARCserver 1000 (8x85MHz, 1GB memory)
>      Solaris 2.5.1
>      NetBackup 3.1
>      StorageTek 9714 tape library (4 x DLT7000)
> 
> I want to move the backup/media server to another platform:
> 
>      Sun E3500 (4x336MHz, 2GB memory, 4 empty Sbus slots)
>      Solaris 7
>      upgrade NetBackup to version 3.4
>      attach same library
> 
> The hostname will *not* move - the new server has a different 
> hostname.
> 
> Has anybody performed a similar rehost? What are the steps to 
> take and what
> are the major issues?
> 
> 
> jd
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu