On Wed, 19 Nov 2008, Rusty.Major AT sungard DOT com wrote:

> The way we have done it several times here is to get everything ready on
> the new server from an OS and hardware perspective. Make sure your
> hostname on the new server is the same as what NBU knows and install NBU
> and patch it up to the same version. Once you're ready to go live, shut
> down NBU on the original server and tar the /usr/openv directory up and
> copy it over to the new server. Untar the tarball to /usr/openv (if you're
> fancy you can do this all in flight).  Give the new master the original
> IPs (or update all other media servers and clients in your environment or
> DNS if you run that) and test network communication. If you have any
> drives/libraries/external storage zoned to your Master you will need to
> make the necessary hardware and SAN changes and update the global device
> db.
>
> It's a pretty simple process and, to me, the trickiest part is making sure
> the OS changes are made properly and are persistent. I will mention that
> we have only done this process with 5.1 MP5/6 moving from Solaris 8/9 to
> Solaris 10. Once you get it done, I'd let it cook for a bit before
> upgrading to make sure there aren't any surprises lurking that might
> surface during or after the upgrade. Besides, depending on your catalog
> size, this one step could take the better part of a day.
>
> Good luck!

I have done something similiar (Solaris 8) -> Solaris 10, it turned out some
of the old jni fiber cards failed to initialize/work properly under 10.

Watch out for hardware compatibility if you use the master as a media server
especially!

Justin.

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