Veritas-bu

Re: [Veritas-bu] Netbackup Move

2008-12-14 00:38:39
Subject: Re: [Veritas-bu] Netbackup Move
From: "Martin, Jonathan" <JMARTI05 AT intersil DOT com>
To: "Mike Day" <mike.day AT inovis DOT com>
Date: Sun, 14 Dec 2008 00:29:38 -0500
Disagreeing with Ed is usually bad juju but in this case I've done several doman migrations on Master/Media running 5.1 and 6.0 without issue on Windows 2003.  Netbackup doesn't seem to care that your host's FQDN is changing from server.domain.xyz to server.domain.abc.  As long as your clients forward / reverse DNS is working everything should be fine.  If your client's bp.confs are using the FQDN then yes you will need to change this on all your clients.
 
Further, its not the cleanest thing in the world but if you absolutely had to change your server's name despite the woeful news below you can still happily do restores from your catalog, you just have to manage your IMAGES folder manually and take care not to overwrite the media.  This is the back bone of my current DR technique and I've tested it several times and it works flawlessly.
 
Finally, your master server does not care where data gets restored to so you can change the name and domain of both your master and client and you will still be able to restore data. Per my note above, just note than changing the master's name makes things tricky.  As usual make sure you have a complete catalog backup before you do anything.
 
Good luck!  If you get stuck give me a shout.
 
-Jonathan


From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Ed Wilts
Sent: Saturday, December 13, 2008 11: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:
 
 
  1. 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
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
<Prev in Thread] Current Thread [Next in Thread>