[Veritas-bu] Java GUI Console Issues (RESOLUTION)
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. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Java GUI Console Issues (RESOLUTION)
... or you could fix your broken DNS. ;^ -- Gabriel Rosenkoetter Radian Group Inc, Senior Systems Engineer gabriel.rosenkoet...@radian.biz, 215 231 1556 From: rusty.ma...@sungard.com [mailto:rusty.ma...@sungard.com] Sent: Wednesday, September 23, 2009 11:57 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Java GUI Console Issues (RESOLUTION) 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. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Java GUI Console Issues (RESOLUTION)
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. :^) -- Gabriel Rosenkoetter Radian Group Inc, Senior Systems Engineer gabriel.rosenkoet...@radian.biz, 215 231 1556 From: Rosenkoetter, Gabriel Sent: Wednesday, September 23, 2009 12:58 PM To: 'rusty.ma...@sungard.com'; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Java GUI Console Issues (RESOLUTION) ... or you could fix your broken DNS. ;^ -- Gabriel Rosenkoetter Radian Group Inc, Senior Systems Engineer gabriel.rosenkoet...@radian.biz, 215 231 1556 From: rusty.ma...@sungard.com [mailto:rusty.ma...@sungard.com] Sent: Wednesday, September 23, 2009 11:57 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Java GUI Console Issues (RESOLUTION) 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. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Java GUI Console Issues (RESOLUTION)
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. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Rosenkoetter, Gabriel Sent: Wednesday, September 23, 2009 13:27 To: Rosenkoetter, Gabriel; rusty.ma...@sungard.com; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Java GUI Console Issues (RESOLUTION) 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. :^) -- Gabriel Rosenkoetter Radian Group Inc, Senior Systems Engineer gabriel.rosenkoet...@radian.biz, 215 231 1556 From: Rosenkoetter, Gabriel Sent: Wednesday, September 23, 2009 12:58 PM To: 'rusty.ma...@sungard.com'; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Java GUI Console Issues (RESOLUTION) ... or you could fix your broken DNS. ;^ -- Gabriel Rosenkoetter Radian Group Inc, Senior Systems Engineer gabriel.rosenkoet...@radian.biz, 215 231 1556 From: rusty.ma...@sungard.com [mailto:rusty.ma...@sungard.com] Sent: Wednesday, September 23, 2009 11:57 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Java GUI Console Issues (RESOLUTION) 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/ 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. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Java GUI Console Issues (RESOLUTION)
Only read the post quickly but have you added an alias using nbemmcmd ? bash-3.00# nbemmcmd -machinealias NBEMMCMD, Version:6.5.3 The following option is required and was not specified: machinetype Usage: nbemmcmd -machinealias [-brief] [-addalias -alias string -machinename string] [-deletealias -alias string] [-deleteallaliases -machinename string] [-getaliases -machinename string] -machinetype api | app_cluster | cluster | master | media | ndmp Command did not complete successfully. bash-3.00# Rosenkoetter, Gabriel gabriel.rosenkoet...@radian.biz Sent by: veritas-bu-boun...@mailman.eng.auburn.edu 24/09/2009 06:26 AM To Rosenkoetter, Gabriel gabriel.rosenkoet...@radian.biz, rusty.ma...@sungard.com rusty.ma...@sungard.com, veritas-bu@mailman.eng.auburn.edu veritas-bu@mailman.eng.auburn.edu cc Subject Re: [Veritas-bu] Java GUI Console Issues (RESOLUTION) 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. :^) -- Gabriel Rosenkoetter Radian Group Inc, Senior Systems Engineer gabriel.rosenkoet...@radian.biz, 215 231 1556 From: Rosenkoetter, Gabriel Sent: Wednesday, September 23, 2009 12:58 PM To: 'rusty.ma...@sungard.com'; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Java GUI Console Issues (RESOLUTION) ... or you could fix your broken DNS. ;^ -- Gabriel Rosenkoetter Radian Group Inc, Senior Systems Engineer gabriel.rosenkoet...@radian.biz, 215 231 1556 From: rusty.ma...@sungard.com [mailto:rusty.ma...@sungard.com] Sent: Wednesday, September 23, 2009 11:57 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Java GUI Console Issues (RESOLUTION) 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. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This e-mail is sent by or on behalf of the named sender identified above. If: (a) you do not wish to receive any e-mail marketing material from this person in the future, please forward the contents of this email to unsubscr...@nab.com.au with the word unsubscribe in the subject box. (b) you wish to unsubscribe from all central e-mail marketing lists used by our business, please forward the contents of this e-mail to unsubscribe...@nab.com.au with the message unsubscribe from all central e-mail marketing lists in the subject box. If you do not forward the contents of this e-mail with your unsubscription then it may not be able to be implemented. The information contained in this e-mail communication may be confidential. You should only read, disclose, re-transmit, copy, distribute, act in reliance
