I had similar issues with short names randomly popping up in my 6.5.3 environment.  In case this helps, here is how to change to the FQDN within EMM:

 

First, get a listing of the hosts in the EMM database:
1) nbemmcmd -listhosts
NBEMMCMD, Version:6.5.3
The following hosts were found:
server          master01.bos.ralph.net
master          master01.bos.ralph.net
media           media01
Command completed successfully.

Next, run the rename command:
2) nbemmcmd -renamehost -machinename media01 -machinetype media -newmachinename media01.bos.ralph.net

Confirm the change was implemented:
3) nbemmcmd -listhosts
NBEMMCMD, Version:6.5.3
The following hosts were found:
server          master01.bos.ralph.net
master          master01.bos.ralph.net
media           media01.bos.ralph.net
Command completed successfully.

 

 

 

Actually, as I was looking over some stale-but-still-open cases I have with Symantec earlier today, I realized that my snark may be misplaced.

 

There are certain places where NBU will insist on using the shortname for a master or media server, because that's how it's stored in EMM, even if a given host lists the master and media servers in its local configuration by FQDN. The circumstance that I've run into is when trying to perform backups of Active Directory servers with the "granular recovery" option enabled: the majority of System State was simply not backed up, the cause for which came down to the client retrieving the name of the master server to which to send the granular data through EMM (rather than its own config) and then being unable to contact that master server because it cannot resolve the FQDN of the master server that, from AD's point of view, lives in a different "domain" and, for reasons I'll never fully understand, AD has naming and security policy intertwined in such a way that it breaks things to have a given domain controller appear in a domain controlled by some other DC. So then no data got sent without enabling the client side to resolve short names into the "outside" domain in some way.

 

(And, of course, I was kidding anyway, Rusty. Just so that part's clear. :^>)

 

 

 

... or you could fix your broken DNS. ;^>

 

--

Gabriel Rosenkoetter

Radian Group Inc, Senior Systems Engineer

gabriel.rosenkoetter AT radian DOT biz, 215 231 1556

 

 

I just completed another upgrade from 5.1 to 6.5 and ran into another issue with getting the Java GUI Console to operate. I ended up adding the FQDN as an alias to the shortname in my hosts file and the problem went away. I would also recommend this as a first step for any issues you have with the Java GUI, such as some panels not working, blank screens after logging in, etc.

Just wanted to put this out there in case someone else had issues as it sure is frustrating to complete an upgrade successfully, only to have problems with the Java Console.

Rusty Major, MCSE, BCFP, VCS ▪ Sr. Storage Engineer ▪ SunGard Availability Services ▪ 757 N. Eldridge Suite 200, Houston TX 77079 ▪ 281-584-4693
Keeping People and Information Connected® ▪ http://availability.sungard.com/
P Think before you print
CONFIDENTIALITY:  This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited.  If you received this e-mail in error, please notify the sender and delete this e-mail from your system.