Your master server can be put in the new domain. All you
need to do is make sure there is a DNS entry OR /etc/hosts file entry for
the old domain on the master server.
If your master server is on IP 123.123.123.123
/etc/hosts
123.123.123.123 masterserver.olddomain.com masterserver.newserver.com masterserver
This will fool NBU and allow the domain change. We had a
domain migration from our old domain to a new domain and this is what I had to
do on the masterserver. All my clients would need the same hosts file
entry which would be a pain to maintain if the IP ever had to be changed so we
just maintained a DNS entry for the old domain and the master server.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu]
On Behalf Of Mike Day
Sent: Saturday, December 13, 2008 9:19 PM
To: Ed Wilts
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Netbackup Move
I knew the hostname was critical, and that was why I was not
going to change it. My knowledge of domains is on the Windows side so I
didn’t think changing the server name from
‘netbackup.old.com’ to ‘netbackup.new.com’ when both
Windows AD domains are fully trusted.
The old domain was to be retired eventually but I should be
able to keep the hostname = ‘netbackup.old.com’ if that is
necessary. We can always just run the old Windows DC on a vmware server
since this will be the only server left.
After the backups are setup and running smoothly for a few
weeks I intend to upgrade to Netbackup 6.5 or the latest version. The
retention of the tapes from my catalog that I need to keep from the old office
is one year. Can I change the name to ‘netbackup.new.com’
after that media retires?
I suppose I should be able to create an alias in AD Windows
DNS to ‘netbackup.new.com’ if necessary so that seems like I need
to add that to my steps so I can resolve the new clients to the
‘netbackup.new.com’ name. Correct?
Is that the only obvious problem with my plan? I can
keep the old domain.
Thanks for your reply!
From: Ed Wilts [mailto:ewilts AT ewilts DOT org]
Sent: Saturday, December 13, 2008 8:30 PM
To: Mike Day
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Netbackup Move
On Sat, Dec 13, 2008 at 6:23 PM,
Mike Day <mike.day AT inovis DOT com>
wrote:
On Monday I will be moving my Netbackup server to a
new office.
I've never done a move like this
but it seems to me like this should not be difficult. Here are the steps
I think I need to do:
2.
Change the 1st 'Server =' line to the name
of the server on the 'bp.conf'. It will have the same server name but the
domain will be a new trusted domain.
This suggests to me that you're changing the name of the master server.
This is not supported and simply changing the host name like this will *NOT*
work.
Since I will be using the same
catalog I will be able to restore the files from my old clients to the new
clients if necessary. I will be using the same LTO-3 tapes from the other
office. The only stuff I think I will need to restore are the from the
Windows Exchange server which moved to the same office Netbackup is moving to a
few weeks ago and a Windows file server that is being moved to a different
office.
If the master server name changes, your original catalog will not work.
There are embedded server names in the various files, including the device
manager. The fully qualified master server name must not change. A
few people have done it without Symantec Professional Services but it's
non-trivial and it's very unlikely you'll have a detailed task list in place by
Monday.
.../Ed
Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
ewilts AT ewilts DOT org