Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

NetBackup 7.5 Ports

Created: 09 Dec 2012 • Updated: 18 Dec 2012 | 13 comments
This issue has been solved. See solution.

Hi,

I am little confusing with net backup ports, “master backup server is Solaris 10” and the client is windows 7 64-bit, I want to backup that client & install JAVA console on it, is the following correct:

  • From Master-server to Client: (13724 – 1556 – 1383 – 13722)

  • From Client to Master-server: (2821 – 1556 – 13783 – 1324 )

 

And do I need the following ports: (13782 – 6106 – 443 – 1500)? Why?

 

Thanks a lot

 

 

Comments 13 CommentsJump to latest comment

RamNagalla's picture

hi 

you would need 13782 also for because its bpcd port no, master/media -- to client and client to master/media

Java/Windows admin consoles to master and media servers requires the TCP ports for vnetd 13724 and PBX 1556 bidirectional.

Client to master server requires the TCP port for vnetd 13724 for client-initiated, not server-initiated, operations. Accordingly, it is generally best to open vnetd bidirectional in case client-initiated operations are needed at a future date.

this T/N would help you identify the ports

http://www.symantec.com/business/support/index?pag...

mph999's picture

 

You can see the ports you need in the security and encryption guide
 
http://www.symantec.com/docs/DOC5185
 
The only port needed is 1556 (pbx) bi-directional.
 
Other ports (vnetd / bpcd) could be used if pbx connection failed, but they should not be needed.
 
You would need a couple of other ports if using NBAC, but you do not mention this.
 
Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Marianne's picture

I agree with Martin. NBU 7.5 needs 1556 only.

See the bottom part of this TN for 7.0.1 (onwards) and 7.1 (onwards) port requirements: 

http://www.symantec.com/docs/TECH136090 

 

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

mb_jedsv's picture

Dears,

port#1556 is opened but i couldn't take a backup for that client "Windows 7 - 64bit" i got Stats "58" ? 

Marianne's picture

Status 58 can be port issues or reverse name lookup issue on the client.

Check that Windows Firewall is disabled on your client.

Perform the following test:

Create bpcd folder under ...\netbackup\logs\ on the client.

On Master and media server, run the following command:

bptestbpcd -client <client-name> -verbose

Check output for errors as well as log file in client's bpcd log file.

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

SOLUTION
mph999's picture

Further to Mariannes post, do you have a 'SERVER = <media server>' entry on the client ?  + as Marianne says, the client and media server must be able to forward/ reverse lookup each others names.

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
mb_jedsv's picture

I got:

 

<16>bptestbpcd main: Function ConnectToBPCD(10.131.xx.xx) failed: 25

cannot connect on socket

 

Marianne's picture

Please provide the following:

1. Confirmation that Windows firewall is disabled on client.

2. Output of bptestbpcd with '-verbose' as well as '-debug' options.

3. Client's bpcd log file as File attachment

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

mb_jedsv's picture

1- Windows firewall is disabled on client

 

2- *

*Output of bptestbpcd with '-verbose': bptestbpcd main: Function ConnectToBPCD(10.131.xx.xx) failed: 25.

*Output of bptestbpcd with '-debug :

14:02:32.623 [29760] <2> bptestbpcd: VERBOSE = 0

14:02:32.638 [29760] <8> file_to_cache_item: [vnet_addrinfo.c:6555] fopen() failed ERRNO=2 FILE=/usr/openv/var/host_cache/163/2118363+veritas_pbx,1,4,2,2,0+10.131.7.117.txt

14:05:43.596 [29760] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 145 0x91

14:08:55.646 [29760] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 145 0x91

14:12:08.678 [29760] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ERROR returned 145 0x91

14:12:42.679 [29760] <8> async_connect: [vnet_connect.c:1219] ran out of time before connect 610 0x262

14:12:42.680 [29760] <16> connect_to_service: connect failed STATUS (18) CONNECT_FAILED

        status: FAILED, (44) CONNECT_TIMEOUT; system: (150) Operation now in progress; FROM 0.0.0.0 TO 10.131.xxx.xxx 10.131.xxx.xxx bpcd VIA pbx

14:12:42.680 [29760] <8> vnet_connect_to_bpcd: [vnet_connect.c:279] connect_to_service() failed 18 0x12

14:12:42.680 [29760] <2> local_bpcr_connect: Can't connect to client 10.131.xxx.xxx

14:12:42.680 [29760] <2> ConnectToBPCD: bpcd_connect_and_verify(10.131.xxx.xxx, 10.131.xxx.xxx) failed: 25

<16>bptestbpcd main: Function ConnectToBPCD(10.131.xxx.xxx) failed: 25

14:12:42.681 [29760] <16> bptestbpcd main: Function ConnectToBPCD(10.131.xxx.xxx) failed: 25

<2>bptestbpcd: cannot connect on socket

14:12:42.681 [29760] <2> bptestbpcd: cannot connect on socket

<2>bptestbpcd: EXIT status = 25

14:12:42.681 [29760] <2> bptestbpcd: EXIT status = 25

cannot connect on socket

 

3- Client's bpcd log file ( i have no idea how to do this step ) , i found : C:\Program Files\Veritas\NetBackup\bin , but what shoud i do after that?

 

 

Marianne's picture

You will find a 'logs' folder under C:\Program Files\Veritas\NetBackup. 

Create a folder called bpcd under logs.
(Full path will be C:\Program Files\Veritas\NetBackup\logs\bpcd)

Run bptestbpcd on server again (bptestbpcd -client <client-name> -debug -verbose). 
Check if log file is created in Client's bpcd log folder.

 

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

mph999's picture

For bpcd logs you need parts 2 and 3 below ...

 

There are two types of logs in NetBackup.  Legacy logs and VX logs.
 
 
1) Creating Legacy Logs
2) Setting Verbose Level for Legacy Logs
3) Collecting Legacy Logs
4) Creating VX Logs and setting the log level
5) Collecting VX logs
6) Volmgr Logs
 
 
1) Creating Legacy Logs
************************
 
These are created in either 
 
Unix
/usr/openv/netbackup/logs/
/usr/openv/volmgr/debug/
 
Windows
<install path>\veritas\netbackup\logs
<install path>\veritas\volmgr\debug
 
 
For example to create bptm log, simply create a directory called the <process> name.
 
mkdir /usr/openv/netbackup/logs/bptm
 
A newly created log will not log anything /detect a change of verbose level until the process is restarted.  For logs such as bptm, this will be when the next backup runs.  Other logs such as bprm and bpdm may require a restart of the NBU services.  I say 'may', if the process starts a child process, then this would write to a newly created log or pick up a verbose level change.
 
 
2) Setting Verbose Level for Legacy Logs
****************************************
 
There are two ways this can be done :
 
(Unix) 
 
To increase the verbose level of all logs (except vault)
Add the entry VERBOSE = <level> into /usr/openv/netbackup/bp.conf.  <level> is a value between 0 and 5, with 5 being the highest.
 
 
(Windows)
 
On the server you are gathering the logs from, run the BAR GUI
From the File menu, select Client Properties and in the pop-up window, goto the Troubleshooting tab.
Set General to 2 and Verbose to 5
 
 
3) Collecting Legacy Logs
*************************
 
The log file is simply found in the <process> name directory.  There is one log per day.
 
The name of the log file will be log.<date>
 
If you are sending multiple log files in, they will all have the same name.  Please therefore rename the log files to :
 
<process>.log.<date>
 
 
4) Creating VX Logs and setting the log level
**********************************************
 
These are more complex, and have to be set with specific commands.  NOTE: Some of these logs, for example, 'mds' do NOT create a log file.  Instead the lines are entered in to other log files.  In the case of mds (143), it logs into EMM (111).
 
 
The vxlogs cover various processes, for example, nbemm, nbrb, nbjm, nbrb, mds
 
 
To set these up on either Unix or Windows, use this command :
 
vxlogcfg -a -p 51216 -o <oid> -s DebugLevel=<1-6> -s DiagnosticLevel=<1-6>
 
For example, to set the EMM and MDS logs to levels 6 and 6 use
 
vxlogcfg -a -p 51216 -o 111 -s DebugLevel=6 -s DiagnosticLevel=6
vxlogcfg -a -p 51216 -o 143 -s DebugLevel=6 -s DiagnosticLevel=6
 
 
To confirm the log level has been set, simply look in the nblog.conf file, which is located in the netbackup diorectory.
(NOTE: DO NOT EDIT THIS FILE MANUALLY)
 
 
5) Collecting VX Logs
*********************
 
 
 
To collect the vx logs, use the nbcplogs command.  This copies the raw logs, which is the preference of Technical Support.
 
NOTE:  The destination directory MUST be empty.
 
 
nbcplogs --no-nbsu -d 2hrs --logs nbemm,nbjm /tmp/logs   (Ex.  Coleect the past 2 hrs of logs, RELATIVE, to when the command is run )
  
nbcplogs --no-nbsu -s 07/11/2012-10:17:58 -e 07/11/2012-12:17:58 --logs nbjm,nbpem /tmp/logs (Collect the logs between two times -s <start> -e <end>  )
 
In these examples, the nbpem and nbjm logs would be copied to /tmp/logs
 
 
For details of using vxlogview please see TN:  http://www.symantec.com/docs/TECH75805
 
 
6) Volmgr Debug Logs
********************
 
These are very similar to legacy logs, the difference being the location and the verbose setting.
There is no value for verbose level, simply it is turned up by adding the work VERBOSE to a line in the vm.conf file.
 
To turn on Media Manager logging:
 
UNIX:
 
Add VERBOSE to the /usr/openv/volmgr/vm.conf file.  If this file does not exist, just create it.
If necessary, create the directory /usr/openv/volmgr/debug
 
mkdir /usr/openv/volmgr/debug/acssi
mkdir /usr/openv/volmgr/debug/acsd
mkdir /usr/openv/volmgr/debug/robots
mkdir /usr/openv/volmgr/debug/daemon
mkdir /usr/openv/volmgr/debug/ltid
mkdir /usr/openv/volmgr/debug/oprd
mkdir /usr/openv/volmgr/debug/reqlib
mkdir /usr/openv/volmgr/debug/tpcommand
 
The following empty files increase the details logged further
 
touch /usr/openv/volmgr/DRIVE_DEBUG
touch /usr/openv/volmgr/ROBOT_DEBUG 
touch /usr/openv/volmgr/AVRD_DEBUG 
touch /usr/openv/volmgr/SSO_DEBUG 
 
 
Restart ltid :
 
/usr/openv/volmgr/bin/stopltid
/usr/openv/volmgr/bin/ltid -v
 
 
Windows:
 
Add VERBOSE to the <install path>\veritas\volmgr\vm.conf file.  If this file does not exist, just create it.
If necessary, create the directory /usr/openv/volmgr/debug
 
<install path>\veritas\volmgr\debug/acssi
<install path>\veritas\volmgr\debug/acsd
<install path>\veritas\volmgr\debug/robots
<install path>\veritas\volmgr\debug/daemon
<install path>\veritas\volmgr\debug/ltid
<install path>\veritas\volmgr\debug/oprd
<install path>\veritas\volmgr\reqlib
<install path>\veritas\volmgr\debug\tpcommand
 
Create the following empty files to increase the details logged further
Ensure that windows does not craete a 'suffix', for example .txt
 
<install path>\veritas\volmgr\DRIVE_DEBUG
<install path>\veritas\volmgr\ROBOT_DEBUG 
<install path>\veritas\volmgr\AVRD_DEBUG 
<install path>\veritas\volmgr\SSO_DEBUG 
 
 
Restart ltid :
 
<install path>\veritas\volmgr\bin/stopltid
<install path>\veritas\volmgr\bin/ltid -v
 
 

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
mb_jedsv's picture

Thank you guys for helping me , and sorry for delay , I spent time to open some ports that mentioned by "Martin" , and I found lookup issue on the client that mentioned by "Marianne van den Berg" . after that I could take a backup.

thank you again

Best Regard

mph999's picture

Excellent.
Please be kind enough to mark the post that helped you the most as the solution.

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805