Video Screencast Help

Is NetBackup installed with FQDN or simple name?

Created: 10 Oct 2012 • Updated: 14 Jan 2013 | 9 comments
This issue has been solved. See solution.

Hello All,

We're in the process of migrating domains. I understand that if NetBackup was setup using simple names and not the FQDN the process is simple. Is there any official tech notes regarding this? 

Could someone confirm if our installtion is using simple names or FQDN? The output below seems to suggest both.

Thanks in advance.

 

Output from nbemmcmd -listhosts -verbose

 

 

C:\Users\admin>nbemmcmd -listhosts -verbose
NBEMMCMD, Version:7.1
The following hosts were found:
test-backup01
        MachineName = "test-backup01"
        FQName = "test-backup01"
        MachineDescription = ""
        MachineNbuType = server (6)
test-backup01
        ClusterName = ""
        MachineName = "test-backup01"
        FQName = "test-backup01"
        GlobalDriveSeed = "VEND:#.:PROD:#.:IDX"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x7
        MachineNbuType = master (3)
        MachineState = active for tape and disk jobs (14)
        NetBackupVersion = 7.1.0.3 (710300)
        OperatingSystem = windows (11)
        ScanAbility = 5
test-backup03
        ClusterName = ""
        MachineName = "test-backup03"
        FQName = "test-backup03"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0xa7
        MachineNbuType = media (1)
        MachineState = active for tape and disk jobs (14)
        MasterServerName = "test-backup01"
        NetBackupVersion = 7.1.0.3 (710300)
        OperatingSystem = windows (11)
        ScanAbility = 5
testlonpo02
        MachineName = "testlonpo02"
        FQName = "testlonpo02"
        MachineDescription = ""
        MachineFlags = 0x1
        MachineNbuType = ndmp (2) (snapvault)
test-backup04
        ClusterName = ""
        MachineName = "test-backup04"
        FQName = "test-backup04"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0xa7
        MachineNbuType = media (1)
        MachineState = active for tape and disk jobs (14)
        MasterServerName = "test-backup01"
        NetBackupVersion = 7.1.0.3 (710300)
        OperatingSystem = windows (11)
        ScanAbility = 5
test-backup02
        ClusterName = ""
        MachineName = "test-backup02"
        FQName = "test-backup02.test.not.real.net"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0xa7
        MachineNbuType = media (1)
        MachineState = active for tape and disk jobs (14)
        MasterServerName = "test-backup01"
        NetBackupVersion = 7.1.0.3 (710300)
        OperatingSystem = windows (11)
        ScanAbility = 5
test-vcb
        ClusterName = ""
        MachineName = "test-vcb"
        FQName = "test-vcb.test.not.real.net"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0xa7
        MachineNbuType = media (1)
        MachineState = active for tape and disk jobs (14)
        MasterServerName = "test-backup01"
        NetBackupVersion = 7.1.0.3 (710300)
        OperatingSystem = windows (11)
        ScanAbility = 5
test-backup05
        ClusterName = ""
        MachineName = "test-backup05"
        FQName = "test-backup05.test.not.real.net"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x63
        MachineNbuType = media (1)
        MachineState = active for tape and disk jobs (14)
        MasterServerName = "test-backup01"
        NetBackupVersion = 7.0.1.0 (701000)
        OperatingSystem = linux (16)
        ScanAbility = 5
testlonpo03
        MachineName = "testlonpo03"
        FQName = "testlonpo03"
        MachineDescription = ""
        MachineFlags = 0x1
        MachineNbuType = ndmp (2) (snapvault)
testLDNMGT01
        MachineName = "testLDNMGT01"
        FQName = "testldnmgt01.test.not.real.net"
        MachineDescription = ""
        MachineNbuType = virtual_machine (10)
testlonpo04
        MachineName = "testlonpo04"
        FQName = "testlonpo04"
        MachineDescription = ""
        MachineFlags = 0x1
        MachineNbuType = ndmp (2) (snapvault)
Command completed successfully.
 

Comments 9 CommentsJump to latest comment

Nicolai's picture

I think the official recommendation is FQDN. But if you are migrating domains it may be worth (depending of the circumstances) to go for short name. This require you got DNS and the /etc/resolv.conf search directive 100% correct.

I have used short name for many years.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Cornishpasty02's picture

What I'm confused about is that the output above seems to show simple names and FQDN's. So I'm wondering which it is. I want to use simple names if I can.

The master does show as having a simple name. 

 

Thanks

revaroo's picture

You can use either. If you are using a mixture (which is not recommend) just ensure both FQDN and non-FQDN hostnames are entered into the same IP in the hosts file (or DNS) and you shouldn't have any issues.\

 

Marianne's picture

There is no default. It is up to the person doing the the installation to specify shortname or FQDN. 

I have seen at one customer how some media servers were installed with shortname and some with FQDN. This caused problems to some extent,,, I sat one day and added emm aliases for all media server names so that all could be referenced via either of the name.

IMHO it is best to use shortnames and add aliases for FQDN.

We have seen a number of requests lately to change Domain name. No problem when shortname was used for installation and configuration.
Major problem when master was configured with FQDN. Here a domain name change means changing master server hostname, which needs consulting engagement...

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
Cornishpasty02's picture

So it looks like our master backup01 is installed with a simple name. 

What then is the process to change the domains? 

 

Thanks

Yogesh9881's picture

Master server hostname changing is not recommended & not supported in netbackup ...

If you absolutely must change the master server name, you will need to contact Symantec Consulting Services.

backup01 is look good dont worry about thatsmiley ....

 

If this post has helped you, please vote or mark as solution.

Before break-up, make sure you have a good backup.....  ;-)

Marianne's picture

Simply use nbemmcmd command to add or remove FQDN aliases.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

bbahnmiller's picture

The only warning I would have with short names would be if you ever start using multiple networks for backups. I have seen the short name aliased to the backup NIC name, while the host name of the server is defined as the name of the primary NIC. The only way things work on that particular server is with host name aliases in the hosts file so as to override the default network behavior. Marianne's suggestion about the EMM aliases is very good. Just be careful if you ever multi-home your backup servers.

Mark_Solutions's picture

I usually go for short names but some customers insist on FQDN

They get around multiple networks using DNS zones and the search orders (not an expert so dont know exactly how they do it) but everything uses short names and for each zone the Master and Media Servers are in both zones so the backup zone so that they resolve as master.backup.company.com and clients that do not have a backup network resolve them as master.prod.company.com (something like that anyway - but it all works fine)

If you want to really know if your current setup uses short of FQDN names just open a Windows Admin Console and it shows you at the top what the Master Server classes its "real" name as.

As others have said - if you need to change its name the you need consulting services or if you plan on doing a move / DR proceedure to a new Master you must keep exactly the same name.

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.