STOP!!    WAIT!!

I would advise keeping your current hostname.  It is a nightmare to change it.
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