[Veritas-bu] migration to a new server

All Policy, schedule and client info as well as images are all in the 
/usr/openv/netbackup/db dir. /usr/openv/volmgr/database holds info regarding 
the volume pools.

Dont forget the change the bp.conf file on all clients/media servers to reflect 
the new master server. 
Remember first line is supposed to be :
SERVER = <master server>

Regards, 
Jim Peppas



>  -------Original Message-------
>  From: Dan Dobbs <DDobbs AT mutualmaterials DOT com>
>  Subject: RE: [Veritas-bu] migration to a new server - Followup question
>  Sent: 18 Nov '05 23:11
>  
>  So, the procedure would be to install NetBackup on the new server, and
>  then tar them on the old box, move them over, and unzip these files into
>  their proper directories?
>  
>  How about schedules, clients, all that? Is that encompassed in this
>  plan, or is that a different file system that needs to come over as
>  well?
>  
>  Thanks again!
>  
>  -dd
>  
>  >>> "stefanos" <smpt AT peppas DOT gr> 11/7/2005 3:09:38 AM >>>
>  No , there is no way to do this.
>  Always the request will be from the real  server name. That's why you
>  must
>  put both virtual and real server name to the server list of all
>  netbackup
>  clients (and media servers). As I write this is what the cluster aware
>  installation of netbackup doing. Don't forget the cluster_name in the
>  vm.conf.
>  
>  
>  Stefanos
>  
>  -----Original Message-----
>  From: veritas-bu-admin AT mailman.eng.auburn DOT edu
>  [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of
>  Williams,
>  Kristopher L
>  Sent: Sunday, November 06, 2005 8:29 PM
>  To: smpt AT peppas DOT gr; Dan Dobbs; Veritas-bu AT mailman.eng.auburn DOT 
> edu
>  Subject: RE: [Veritas-bu] migration to a new server - Followup
>  question
>  
>  Stefanos and others,
>  
>  Quick followup question to your last tip.
>  
>  This might be a dumb question, but does anyone know on Windows how to
>  make
>  the "requests" coming from netbackup come from a virtual name. So if
>  my
>  master servers real name is server1.domain.com and I create a virtual
>  name
>  in DNS of nbmaster.domain.com (with a different ip address of course)
>  how
>  can I make sure netbackup is going out using nbmaster.domain.com and
>  not
>  server1.domain.com? Both IP's are bound to the same network card on
>  the
>  server.
>  
>  I've tried to figure this out by just adding in the virtual name to one
>  of
>  my media managers. When looking in the logs all I see if the access
>  denied
>  message for server server1.domain.com.
>  
>  Thanks guys!
>  
>  
>  Kris
>  
>  -----Original Message-----
>  From: veritas-bu-admin AT mailman.eng.auburn DOT edu
>  [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of stefanos
>  Sent: Sunday, November 06, 2005 3:58 AM
>  To: 'Dan Dobbs'; Veritas-bu AT mailman.eng.auburn DOT edu
>  Subject: RE: [Veritas-bu] migration to a new server
>  
>  Well we have install linux master server to a lot of our customers.
>  Both for
>  small and big installations. The bigest is an isp with more than 200
>  network
>  clients, 1master and 1 media server. We had problems with 4.5 but with
>  5.x
>  no problem at all.But this is more personal (and customer) decision.
>  
>  For the migration, don't go through importing. Just copy the
>  /netbackup/db
>  and /volmgr/database directories (exclude the ltidevs robotic_def and
>  globdb) Also DON'T copy the var folder (the license keys are bundle
>  with the
>  server name so if you copy the var folder netbackup will not come up).
>  Take
>  care for any link you may have inside the db folder (images
>  perhaps) and any disk storage unit you may have (for space reasons).
>  Run the ./volmgr/bin/vmglob -set_gdbhost $newmastername And the device
>  configuration wizard only for the master server. Restart netbackup.
>  Any
>  other media server you may have will register the drives himself after
>  some
>  time. (but will be ready for backups immediately) Then run the command
>  bpmedia -newserve $newmastername -oldserver $oldmastername After that
>  the
>  new master server is ready for use.
>  
>  Tip. Install the new master server  with a virtual name and a different
>  ip
>  than the server name and ip. This will help any migration in the
>  future. If
>  you do this you must put the original server name to the netbackup
>  server
>  list of all systems and to put the "cluster_name = $virtualname" to
>  the
>  vm.conf file of the master server (This is equivalent to one node
>  cluster
>  installation and helps to migrate muster server between systems
>  eliminating
>  the  "name problem")
>  
>  stefanos
>  
>  -----Original Message-----
>  From: veritas-bu-admin AT mailman.eng.auburn DOT edu
>  [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Dan
>  Dobbs
>  Sent: Saturday, November 05, 2005 12:30 AM
>  To: Veritas-bu AT mailman.eng.auburn DOT edu
>  Subject: [Veritas-bu] migration to a new server
>  
>  Greetings, all.
>  
>  Currently, we are running 5.1 on an HP-UX L-class box, with a couple
>  'bots
>  (one old Surestore juke with (4) DLT4000s, one Neo juke with a DLT220).
>  It
>  seems to work reasonably well. We have a few hundred tapes 'in
>  circulation'.
>  So, we're probably one of the smaller sites that visit this list. :>)
>  
>  We're taking the plunge, and planning a migration of our backup
>  environment
>  to Red Hat Linux (the HP-UX maint fees will pretty much pay for the
>  change).
>  
>  My thought on migration was to hook the Neo juke up to the new RH box,
>  install Netbackup with the new servername, and import the SDLT tapes
>  (around
>  thirty). When they have been satisfactorily imported into the new
>  server's
>  database, backup the catalog on the old box, and then delete the media
>  from
>  the HP-UX box.
>  
>  Then, we'd run the boxes simultaneously for a while, and once we feel
>  confident with the new server, follow the same basic operation with
>  the
>  'regular' dlt's and the other juke and decommission the HP-UX box.
>  
>  It would appear that this isn't all that different than a disaster
>  recovery
>  scenario, exc that I can't re-use the catalog as the server name is
>  different (and I've always hated the current name of the backup server
>  anyway).
>  
>  What other recommendations/caveats could you folks suggest? I'm sure
>  that
>  I've missed a slew of things. :>)
>  
>  Cheers,
>  
>  -dd
>  _______________________________________________
>  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
>  
>  
>  
>  _______________________________________________
>  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
>