Maybe add aliases so both FQDN and short name are in EMM Db.
Check TCP wrappers etc – anything that can block traffic (unlikely).
Bptestnetconn ?
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu]
On Behalf Of Justin Piszcz
Sent: 15 August 2013 22:54
To: 'Peacock Dennis - dpeaco'; 'Rusty Major'; VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Converting standard client to a media server
Hi,
What is returned from the following?
$ sudo /usr/openv/volmgr/bin/vmglob -get_gdbhost
When you ran the nbemmcmd, did you get a successful result?
Example from an older test run on the master server: (this is what fixed it for me when I ran into this issue)
$ sudo /usr/openv/netbackup/bin/admincmd/nbemmcmd -addhost -machinename media-server.test.com -machinetype media -masterserver master-server.test.com
-operatingsystem linux -netbackupversion 7.1
NBEMMCMD, Version:7.1
Command completed successfully.
$
Is the bp.conf ‘sane’ on the client host can you paste it here after filtering it out the names etc?
Justin.
Yup. Did all that.
J
Dennis Peacock
Data Protection and Recovery Engineer
Acxiom Corporation
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu]
On Behalf Of Rusty Major
Sent: Thursday, August 15, 2013 4:47 PM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Converting standard client to a media server
Hey Dennis,
Did you change the IP or hostname?
clear host cache (bpclntcmd -clear_host_cache) on all boxes?
Can you run nbemmcmd -listhosts from the new media server?
Did you manually add the new media server to the master:
./nbemmcmd -addhost -machinename <newmedianame> -machinetype -media -masterserver <mastername> -operatingsystem <os type> -netbackupversion <version>
I think that's what the command is.
I'm sure you've done all that, but thought I would throw it out there.
On Thu, Aug 15, 2013 at 4:25 PM, Dennis Peacock <nbu-forum AT backupcentral DOT com> wrote:
Netbackup 7.5.0.5
Both boxes are RedHat Linux Release 6
Box "A" is the master and has always been the master/media server.
Box "B" has always been a standard client backing up across the network.
Licensing purchased and Box "B" was cleanly installed as a media server.
The master server can't see Box "B" as a media server.
bp.conf file checked and tweaked on both boxes.
Netbackup has been stopped and restarted several times.
Tried to manually add it to the master and I get this message:
globalDB hostname has not been set (Status 4)
4 of us have tried to get this working.....all have failed so far.
Tips, pointers, tricks, advice......all would be appreciated.
+----------------------------------------------------------------------
|This was sent by dpeaco AT acxiom DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--
Rusty Major ▪ Technical Architect and Team Lead - Backup Infrastructure Engineering ▪ Sungard Availability Services ▪ 757 N. Eldridge Pkwy., Suite 200, Houston,
TX 77079 ▪ 281-584-4693 ▪ Cell 713-724-4914 ▪ rusty.major AT sungard DOT com
------------------------------------------------------------------------------
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.
***************************************************************************
The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be legally
privileged.
If the reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.
If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.
Thank You.
****************************************************************************
