02-13-2012 10:50 PM
Hi Guys,
We are looking at migrating an old legacy DNS zone to the main DNS zone. Our Master server is currently located in the legacy DNS zone.
Is there anything I need to look out for when migrating the Master server between DNS zones?
The Server name and IP will remain the same, obviously the FQDN will change but otherwise it will remain the same. Clients are configured to only use the hostname of the Master server, there might be a couple that use the FQDN but these can be changed as required.
Current config:
Netbackup 7.1.0.3
Solaris 10 Master/Media Server - Tape Library and Staging Disks connected. - located in the legacy DNS zone
Windows 2k8 Media/Storage server for Deduplication. - located in the Main DNS zone
Thanks
Dan
02-14-2012 12:30 AM
How is NBU configured? Shortname or FQDN?
Run nbemmcmd -listhosts -verbose
If master is showing shortname, all is well.
If FQDN, use nbemmcmd to add alias for shortname.
02-14-2012 08:57 PM
Thanks Marianne,
The MachineName and FQName are both set to use the FQDN.
Once I add an alias for the shortname, will I have to remove the old FQDN once we migrated zones?
02-14-2012 09:52 PM
If you don't mind - please show us output of nbemmcmd -listhosts.
Feel free to change names e.g. master.domain for FQDN or master for shortname.
02-15-2012 05:54 PM
Hi Marianne,
Here are the results, I've changed the names to MasterServer.domain and MediaServer.domain
There was no short name mentioned anywhere.
bash-3.00# nbemmcmd -listhosts
NBEMMCMD, Version:7.1
The following hosts were found:
server MasterServer.domain
master MasterServer.domain
ndmp MasterServer.domain
media MediaServer.domain
ndmp MediaServer.domain
Command completed successfully.
bash-3.00# nbemmcmd -listhosts -verbose
NBEMMCMD, Version:7.1
The following hosts were found:
MasterServer.domain
MachineName = "MasterServer.domain"
FQName = "MasterServer.domain"
MachineDescription = ""
MachineNbuType = server (6)
MasterServer.domain
ClusterName = ""
MachineName = "MasterServer.domain"
FQName = "MasterServer.domain"
GlobalDriveSeed = "VEND:#.:PROD:#.:POS"
LocalDriveSeed = ""
MachineDescription = ""
MachineFlags = 0xe4
MachineNbuType = master (3)
MachineState = active for tape and disk jobs (14)
NetBackupVersion = 7.1.0.3 (710300)
OperatingSystem = solaris (2)
ScanAbility = 5
MasterServer.domain
MachineName = "MasterServer.domain"
FQName = "MasterServer.domain"
MachineDescription = "PureDisk"
MachineFlags = 0x2
MachineNbuType = ndmp (2) (storage_server)
MediaServer.domain
ClusterName = ""
MachineName = "MediaServer.domain"
FQName = "MediaServer.domain"
LocalDriveSeed = ""
MachineDescription = ""
MachineFlags = 0x4
MachineNbuType = media (1)
MachineState = active for disk jobs (12)
MasterServerName = "MasterServer.domain"
NetBackupVersion = 7.1.0.3 (710300)
OperatingSystem = windows (11)
ScanAbility = 5
MediaServer.domain
MachineName = "MediaServer.domain"
FQName = "MediaServer.domain"
MachineDescription = "PureDisk"
MachineFlags = 0x2
MachineNbuType = ndmp (2) (storage_server)
Command completed successfully.
02-16-2012 01:28 AM
I was hoping to see something like this:
MasterServer
MachineName = "MasterServer"
FQName = "MasterServer.domain"
Life is a lot easier in a situation like this...
In all honesty, I am no longer sure that this can easily be fixed with EMM aliases. It might be perceived as a hostname change.
I will ask my 'expert friends' for their thoughts and advice... Let me 'call a friend'...
02-16-2012 01:46 AM
This does look like a server name change to me so would need catalog / EMM manipulation
Having said that if you have a hosts file entry on the Master server for MasterServer.Domain against it IP address then it will tick along happily without any issues
Likewise hosts files can be used on the Media Servers for them selves and the Master - and I guess the clients may need ones for the Master and Media Server
Hope this helps
02-16-2012 02:33 AM
The Master server is configured with the FQN for the NBU name …
We treat this as the hostname, so as far as I know changing the domain is the 'same' as changing the hostname, and therefore unsupported.
It can possibly be done as a 'consulting' task by one of our 'Partners' , but not be Technical support - we are not allowed to do it, and, do not have access to the scripts used by the consultants.
Martin
02-26-2012 03:50 PM
Sorry for the late reply, been off work for a week. Thanks for the replies everyone.
If the server does get moved and we do try adding the host file entry as Mark suggested, what is the worst case senario if it doesnt work? Do we just move the server back and everything is fine or do i need to move it back and restore the catalog?