It's a lot easier if you don't use the system's actual hostname as the
master server name.  Have a different DNS name for the master server;
this poor-mans clustering allows you move the master server name to
another host, without changing hostnames.  Just down the NIC on one box
and reassign the IP to the other.  Helps to have a multi-homed system
and shared disks. 

-----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 David Rock
Sent: Wednesday, October 05, 2005 3:28 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: SV: [Veritas-bu] master server hostname change - what are
the guidelines?

* Hampus Lind <hampus.lind AT rps.police DOT se> [2005-10-05 12:05]:
> As mentioned, many against mails have been posted on this subject.
> 
> However, I have done it a couple of times and so have others.
> 
> The important key here is to really study the steps before and 
> learning exactly what happens. Best is to do it in a lab env a couple
of times first?
> The first time I did this we did get some problems, but it was on 
> clients I missed changed the SERVER name on, so if you are VERY 
> careful and really understands how netbackup works and where to look 
> if you run into trouble then its not that difficult.

Even if you are successful, Symantec does NOT support doing it. It's
messy and nasty and generally something to stay away from. You have to
weigh the pros and cons and decide if the risk of doing something that
is VERY unsupported is worth the effort. If you ever have a problem with
your environment and they find out you did that, all bets are off.

Netbackup has plenty of its own issues, why create more if you don't
have to?

--
David Rock
david AT graniteweb DOT com