Unsolved
This post is more than 5 years old
1 Message
0
1969
March 27th, 2014 16:00
Instructions for moving a linked DataDomain unit to a new IP/DNS suffix
I have 3 DataDomain units, each connected to their own Netbackup server (1 Master, 2 Media) using Lifecycle Policies + BOOST. All Data Domain units are linked and also have replication setup between them.
I need to move 2 of the 3 Data Domain units to a new network. This involves changing their IP, Subnet Mask, Gateway, DNS servers, and DNS suffix.
What order would I have to go in to make the necessary changes on each unit? I read there may be CIFS issues changing the Domain Name, but they aren't connected to Active Directory, so I don't think recreating CIFS information wouldn't be an issue.
No Events found!
JWeinsheimer
91 Posts
1
April 1st, 2014 13:00
I haven't encountered any issues changing basic networking on a DD system. IP, subnet, gateway, DNS info should be pretty straight forward.
If the DNS suffix change also changes the FQDN of the DD system you may run into a few little issues. The first that I've seen is that you need to re-authenticate to active directory which takes all of a minute to do. The other issue I've encountered is that changing the name of a DD system invalidates the local CA certificate. I haven't seen this result in any data availability issues but it will prevent you from managing the the effected systems through another DD's Enterprise Manager. The fix is straightforward though, just remove the DD's from Enterprise Manager and open a ticket with support to manually delete the old certificates. Once that's done they can be added back in.
Beyond that I haven't encountered any issues. If Netbackup is configured to use the FQDN of a DD then simply update the DNS entry for the system and things should proceed once records have been updated. Otherwise you'll have to update Netback to reflect the IP changes. In addition, if you're using any DD Boost interface groups, they will have to be updated as well.