> I haven't been able to find the answer to this question in the SAG...

Be sure you're familiar with the DR procedures section of the
Troubleshooting Guide, and the Release Notes and the Impact Guide as
well (Veritas support site, NetBackup 6 manuals).

Your plan:
-  v5master, v5media, two weeks of backups that you don't care about
-  replace master with new install, same name, trash the backups
-  use v6master with v5media
-  disconnect v6master
-  put v5master back in place and use it
-  re-create your implementation on v6master offlime
-  put v6master back in place next maintenance window?
-  upgrade v5media to v6media next maintenance window?

You are doing a lot of work to set yourself up for failure.  

a.  If you accept a dictate to do this under constraints that do not
allow you to do it in a supported way--not to mention without test and
backout time--well, let's just say there's always a quality way to do
things and that isn't it.  The room isn't on fire, is it?

b.  If you don't care about the old backups, then uninstall v5 and
install v6 on  master and media and be done with it.  It doesn't take
that long to re-create STUs and classes by hand in the GUI, much less if
you script it.

c.  Small-window/do-the-least-harm principle:  catalog backup, replace
oldmaster with newmaster, install v5, bprecover.  Backout is reinstall
oldmaster and bprecover media server if appropriate.  Resume normal
operations until next window.

d.  Do the upgrade by the book.  Open a support call and let Veritas
check current state and your plan.  Catalog backup, upgrade master to
v6, pushdata, usev5hosts, separate catalog backup.  Backout is reinstall
v5 and bprecover.  Resume normal operations.

e.  Upgrade media in a subsequent window, before-and-after catbackups.


> We have an existing windows 5.1MP3 environment with 1 Master 
> and 1 Media
> server. We are tossing our catalog (only 2 weeks right now) 
> so we don't
> intend to do an NBPushdata. We want to take the existing 
> Master off the
> network, then build a 6.0MP3 Master server on new hardware using the
> same IP address and DNS name, "discovering" the Media server 
> and storage units.
> 
> Because of a short maintenance window, we want to then take the new
> Master off the network, and put the old one back in service until the
> next maintenance window. This will allow us to rebuild the policies
> against all needed storage units, volume pools, etc. off 
> line. We'll add
> the clients into the policies during the next maintenance window.
> 
> We've know how to handle all the WWN/alias parameters in the 
> fabric, and
> can deal with the changing windows SID, and MAC addrs for the NIC's.
> What I need to ensure is that the 5.1MP3 media server will still be
> viable after the new Master is built if the old 5.1 Master has to go
> back into play if things go bad or we run out of time.
> 
> We intend to create the volume group and pools on the new server (so
> they can be added to the policies off line), but do not want 
> to add any
> volumes to ensure the Media servers (or old Master server, if 
> it has to
> be re-instated) media manager database doesn't get confused. 
> How does an
> NBU 6.0MP3 Master handle the volumes assigned to an 5.1MP3 
> Media server?
> Does the 6.0 Master take "ownership", or does the 5.1MP3 media still
> have it's database?