Veritas-bu

[Veritas-bu] NetBackup 5.x to 6.x upgrade

2008-03-13 16:14:52
Subject: [Veritas-bu] NetBackup 5.x to 6.x upgrade
From: "JAJA (Jamie Jamison)" <jamisonj AT zgi DOT com>
To: veritas-bu AT mailman.eng.auburn DOT edu
Date: Thu, 13 Mar 2008 11:51:20 -0700
Message: 2
Date: Thu, 13 Mar 2008 15:32:04 +0100
From: "WALLEBROEK Bart" <Bart.WALLEBROEK AT swift DOT com>
Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x
To: <veritas-bu AT mailman.eng.auburn DOT edu>
Message-ID:
        
<CA331BA818F8844EA88A7DCBC0F8307E77C366 AT BE-EXCHANGE-05.swift DOT corp>
Content-Type: text/plain;       charset="us-ascii"


        > It would be much nicer to build the Sol 10 env with a fresh
install of 6.5.1 and just import the 5.0 catalog.

We are plannig to go to 6.5.1 the third quarter of this year.

What we planned however is to place a brand new HP cluster next to the
existing Master Server and install 6.5.1 on this new cluster.  But then
we are stuck with the conversion of the catalog.

Isn't there a way (Symantec tool for example) to convert the catalog to
the new db format and import it ton the new nbu server so not going
through the normal upgrade ?


Best Regards,

Bart WALLEBROEK

Backup admin Swift



------------------------------

I upgraded to 6.0MP4 last year and upgraded my NetBackup master server
from a V880 running Solaris 9 to a T2000 (which is just the cutest piece
of hardware I've ever seen from Sun) running Solaris 10. To avoid
bringing a lot of cruft over which had accumulated on the old backup
Master over the years while getting the catalog upgraded to the new db
format I did the following.

1) Ran the NetBackup utilities to check catalog consistency and worked
with my VAR (DataLink) and Symantec to make sure that I was good to go
for the upgrade.
2) Backed up my catalog (twice).
3) Stopped my NetBackup services on the old NetBackup master.
4) Created a new SAN volume, mounted it on the old NetBackup master and
copied my entire /usr/openv/ hierarchy over to it.
5) Rebooted the old NetBackup master with the mount point for /usr/openv
changed to point at the new /usr/openv duplicate volume.
6) Installed NetBackup 6.0 and ran the upgrade scripts to convert the
catalog db to the new format.
7) Installed the NetBackup maintenance packs to bring the system up to
MP5.
8) Tested to make sure that I could back up and restore files from each
policy type from disk based storage units and tape based storage units.
9) Tested duplication to tape from disk based storage units and restore
from those duplicated copies.
10) Reverted back to MP4 after finding out that Symantec broke NDMP
backups in MP5 (how that MP ever got out of the lab escapes me).

This was time consuming but gave me an easy fall back. If everything had
failed I could have changed the mount point for /usr/openv to point back
at the old mount point, rebooted my master server and I would have been
back at status quo ante.
Once I had 6.0MP4 up, running and tested on the old NetBackup master I
let it run for a week to check performance and while it was doing so
finalized my 6.0MP4 install on the new NetBackup master.

When I did the transition to the new server I did the following.

1) Backed up the catalog, now converted to the new db format, on the old
NetBackup master.
2) Shut the old NetBackup master down and changed the hostname and IP
address of the new NetBackup master to that of the old NetBackup master.
3) Rebooted the new NetBackup master, checked that it came up with the
correct hostname and IP address.
4) Started NetBackup and ran bprecover on my catalog backup tape.
5) Tested as above.

I don't know if this was good practice, or if it was too laborious. I'm
a suspenders and belt kind of guy when it comes to doing upgrades like
this and since I'm long past my days of cowboy'ing it when I do upgrades
like to have as many fallback options as reasonably possible. This did
require some extra SAN storage for a few weeks while I tested things,
and as I've mentioned was perhaps too laborious but other than that it
did allow me to do a clean upgrade and gave me an easy fallback option
at each step along the way. I don't know if this would work in your
environment, mine is pretty small compared to a lot of others, but I
hope it helps.

Jamie Jamison
Network Systems Administrator
ZymoGenetics, Seattle



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

<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] NetBackup 5.x to 6.x upgrade, JAJA (Jamie Jamison) <=