Does anyone have a suggestion for the following scenario that avoids the
difficulties in renaming a NB Master server?

We're upgrading, our old environment looks like this:

Server 1:
        Solaris 8
        Samba File Server
        Netbackup 6.0mp2 Master Server.
        HVD SCSI DLT7000 Library (legacy backups)
        FC LTO-3 Library (current Backups).

Our target environment:

All servers are now Blades, ie, they have FC connections, but no SCSI.

Server A (With Server 1's name)
        RHEL 4.0
        Samba File Server
Server B
        RHEL 4.0
        Netbackup Master Server
        FC LTO-3 Library (current backups)
Server 1 (Under a new name)
        Solaris 8
        Netbackup Master 
        SCSI DLT7000 (Legacy Backups only)


I had thought to simply move Netbackup to Server B, Samba to Server A,
and rename Server 1. That would have given me a transparent upgrade for
my users, a separate Backup server (finally), and I could have kept the
old server in the corner for legacy recoveries, which would have also
given me a nice reason to split my netbackup catalog between to servers,
and hence speed up current backup catalg searches.

I've discovered that the only way to do this in a Veritas supported
manner, is to move Netbackup to Server A so the hostname doesn't change,
then buy a SCSI-HVD router ($$) to connect the old library to the new
server. 

Does anyone have any better ideas? I'm going to talk to Veritas today
about doing the rename, but from the sounds of things, it'ss going to be
even more painfull in Version 6.0 than it was in 4.x and 5.x.

Thanks,
        Tristan