Error 130 in netbackup

[virankumar]

Few netbackup client 6.5.6 , having 130 error's

Can any one please give me the resolution for this error's

[Nicolai]

General Symantec recommendation to status 130

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

Also check the clients don't have any full file systems and enough memory is available

[inn_kam]

Also Netbackup 6.5* is EOL and EOS

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

[Mujeeb-Arrosoft]

Hi ViranKumar , this Netbackup error 130 is related to system call.

1.Check the NetBackup Problems report for additional information about the error.

2.Check the system log for reported problems.

3.For detailed troubleshooting information, create bpdbm, bptm, and bprd debug log directories on the master server. Increase the unified logging level by using the vxlogcfgcommand.

4.Retry the operation and check the resulting debug logs.

[Marianne]

As indicated above - NBU 6.x ran out of support more than 2 years ago. 
You REALLY need to upgrade.

To troubleshoot status 130, you firstly need to look at the info in Details tab of the failed job.
This will tell you if the problem is on the master, on the media server or on the client.

Tell us which OS and NBU version on the client and post all text in Details tab of failed job.

Create bpbkar log folder on failing clients for further troubleshooting.

[virankumar]

Hello Maria,

Details Job --

--------

Dec 25, 2014 9:06:21 PM - estimated 0 kbytes needed
Dec 25, 2014 9:13:20 PM - Critical bpbrm (pid=5121) from client clientname-bsn: FTL - terminated by signal 12
Dec 25, 2014 9:13:19 PM - connecting
Dec 25, 2014 9:13:20 PM - connected; connect time: 0:00:00
Dec 25, 2014 9:14:54 PM - mounting MP0795
Dec 25, 2014 9:15:05 PM - end writing
system error occurred  (130)

[Marianne]

You forgot to tell us which OS and NBU version on the client.

Issue is with /data:

21:13:20.507 [27562] <4> bpbkar: INF - Processing /data
21:13:20.631 [27562] <32> bpbkar: FTL - terminated by signal 12
21:13:20.631 [27562] <16> bpbkar: ERR - bpbkar FATAL exit status = 130: system error occurred

You need to troubleshoot on the client to see what is wrong with /data.

Use OS tar command to backup this filesystem to /dev/null and see what happens (this will read filesystem without writing anything):

tar cvf /dev/null  /data
or NBU command (first increase logging level on client to at least level 3):
/usr/openv/netbackup/bin/bpbkar -nocont /data >/dev/null 2>&1

Also see: 
How to determine what a system call signal XX means
http://www.symantec.com/docs/TECH27854 

Once the issue with reading this filesystem is resolved, the backup will work.

[virankumar]

Hello Maria,

Solaris - 5.10

Client - NetBackup-Solaris10 6.5.3.1

i tried excude those /dat file from nad restarted the backup but still its showing different filesystems

19:21:26.225 [25290] <4> bpbkar: INF - Inform when done
19:21:26.225 [25290] <4> bpbkar: INF - Echo keepalives
19:21:26.226 [25290] <4> bpbkar: INF - BACKUP START
19:21:26.226 [25290] <4> bpbkar: INF - Estimate:-1 -1
19:21:26.243 [25290] <2> bpbkar add_to_filelist: starting sizeof(filelistrec) <68>
19:21:26.303 [25290] <4> bpbkar: INF - Throttle duration required = 512 usec.
19:21:26.308 [25290] <4> bpbkar: INF - Processing /data
19:21:26.323 [25290] <4> bpbkar: INF - Excluded /data by exclude_list entry /data
19:21:26.323 [25290] <4> bpbkar: INF - Processing /etc/dfs/sharetab
19:21:26.340 [25290] <4> bpbkar: INF - Processing /devices
19:21:26.511 [25290] <4> bpbkar: INF - Processing /
19:21:26.552 [25290] <32> bpbkar: FTL - terminated by signal 12
19:21:26.552 [25290] <16> bpbkar: ERR - bpbkar FATAL exit status = 130: system error occurred
19:21:26.552 [25290] <4> bpbkar: INF - EXIT STATUS 130: system error occurred
19:21:27.343 [25290] <16> bpbkar: ERR - read server exit status = 130: system error occurred
19:21:27.344 [25290] <4> bpbkar: INF - setenv FINISHED=0

[Marianne]

As per previous posts - forget about NBU for now and troubleshoot at OS level.

Nicolai has suggested that you check for full filesystem(s) on this client.

Check on this OS as per TN above what 'signal 12' means. 
Here signal 12 is an OS error, not NBU.

Check /var/adm/messages for errors, check memory and cpu usage, etc... etc....

[Nicolai]

Signal 12 is Bad System Call. 

I am guessing Netbackup is not compatible with the OS version you are using.

Netbackup 6.X Operating System Compatibility List can be found here:

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