backup job failing with erro code 42

Question

Please find the logs for failure of backup JOb

Activity Monitor logs job details :--&gt;

11/17/2015 15:08:07 - Info nbjm (pid=8176) starting backup job (jobid=27665) for client vnmhnned1-bkup, policy vnmhnned1-bkup_FILES, schedule Daily_Incr
	11/17/2015 15:08:08 - estimated 212478 kbytes needed
	11/17/2015 15:08:08 - Info nbjm (pid=8176) started backup (backupid=vnmhnned1-bkup_1447747688) job for client vnmhnned1-bkup, policy vnmhnned1-bkup_FILES, schedule Daily_Incr on storage unit vnmhnobs1-hcart-robot-tld-0
	11/17/2015 15:08:09 - Info bpbrm (pid=7012) vnmhnned1-bkup is the host to backup data from
	11/17/2015 15:08:09 - Info bpbrm (pid=7012) reading file list from client
	11/17/2015 15:08:09 - started process bpbrm (pid=7012)
	11/17/2015 15:08:09 - connecting
	11/17/2015 15:08:10 - Info bpbrm (pid=7012) starting bpbkar on client
	11/17/2015 15:08:10 - Info bpbkar (pid=0) Starting bpstart_notify script
	11/17/2015 15:08:10 - connected; connect time: 0:00:00
	11/17/2015 15:08:22 - Info bpbkar (pid=0) Finished bpstart_notify script
	11/17/2015 15:08:22 - Info bpbkar (pid=25067) Backup started
	11/17/2015 15:08:22 - Info bpbrm (pid=7012) bptm pid: 7035
	11/17/2015 15:08:22 - Warning bpbrm (pid=7012) from client vnmhnned1-bkup: WRN - Old TIR file /usr/openv/netbackup/tir_info//NetBackup_file_info.vnmhnned1-bkup_FILES is missing. Backing up everything in /.
	11/17/2015 15:08:22 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/CORE] is on file system type autofs. Skipping
	11/17/2015 15:08:22 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/GRAN] is on file system type autofs. Skipping
	11/17/2015 15:08:22 - Info bptm (pid=7035) start
	11/17/2015 15:08:23 - Info bptm (pid=7035) using 65536 data buffer size
	11/17/2015 15:08:23 - Info bptm (pid=7035) setting receive network buffer to 262144 bytes
	11/17/2015 15:08:23 - Info bptm (pid=7035) using 30 data buffers
	11/17/2015 15:08:23 - Info bptm (pid=7035) start backup
	11/17/2015 15:08:23 - Info bptm (pid=7035) backup child process is pid 7037
	11/17/2015 15:08:23 - Info bptm (pid=7035) Waiting for mount of media id 5301L4 (copy 1) on server vnmhnobs1.
	11/17/2015 15:08:23 - mounting 5301L4
	11/17/2015 15:09:35 - Info bptm (pid=7035) media id 5301L4 mounted on drive index 1, drivepath /dev/rmt/0cbn, drivename HP.ULTRIUM4-SCSI.001, copy 1
	11/17/2015 15:09:35 - mounted 5301L4; mount time: 0:01:12
	11/17/2015 15:09:35 - positioning 5301L4 to file 1
	11/17/2015 15:09:45 - positioned 5301L4; position time: 0:00:10
	11/17/2015 15:09:45 - begin writing
	11/17/2015 15:09:52 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/dev/.devfsadm_synch_door] is a door file. Skipping
	11/17/2015 15:09:52 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/dev/.zone_reg_door] is a door file. Skipping
	11/17/2015 15:09:52 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/dev/fd] is in a different file system from [/]. Skipping
	11/17/2015 15:09:52 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/devices] is in a different file system from [/]. Skipping
	11/17/2015 15:09:52 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/etc/mnttab] is on file system type mntfs. Skipping
	11/17/2015 15:09:54 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/etc/svc/volatile] is in a different file system from [/]. Skipping
	11/17/2015 15:09:54 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/etc/sysevent/piclevent_door] is a door file. Skipping
	11/17/2015 15:09:54 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/etc/sysevent/sysevent_door] is a door file. Skipping
	11/17/2015 15:09:54 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/etc/sysevent/devfsadm_event_channel/1] is a door file. Skipping
	11/17/2015 15:09:54 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/etc/sysevent/devfsadm_event_channel/reg_door] is a door file. Skipping
	11/17/2015 15:09:54 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/etc/sysevent/syseventconfd_event_channel/reg_door] is a door file. Skipping
	11/17/2015 15:09:54 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/export/CORE] is on file system type NFS. Skipping
	11/17/2015 15:09:54 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/export/GRAN] is on file system type NFS. Skipping
	11/17/2015 15:09:54 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/home] is on file system type autofs. Skipping
	11/17/2015 15:09:58 - Info bpbkar (pid=25067) 5000 entries sent to bpdbm
	11/17/2015 15:09:58 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/lib/libc.so.1] is on file system type lofs. Skipping
	11/17/2015 15:09:58 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/net] is on file system type autofs. Skipping
	11/17/2015 15:10:05 - Info bpbkar (pid=25067) 10000 entries sent to bpdbm
	11/17/2015 15:10:05 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/proc] is on file system type PROC. Skipping
	11/17/2015 15:10:05 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/system/contract] is on file system type ctfs. Skipping
	11/17/2015 15:10:05 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/system/object] is on file system type objfs. Skipping
	11/17/2015 15:10:05 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/tmp] is in a different file system from [/]. Skipping
	11/17/2015 15:10:09 - Info bpbkar (pid=25067) 15000 entries sent to bpdbm
	11/17/2015 15:10:12 - Info bpbkar (pid=25067) 20000 entries sent to bpdbm
	11/17/2015 15:10:17 - Info bpbkar (pid=25067) 25000 entries sent to bpdbm
	11/17/2015 15:10:20 - Info bpbkar (pid=25067) 30000 entries sent to bpdbm
	11/17/2015 15:10:21 - Info bpbkar (pid=25067) 35000 entries sent to bpdbm
	11/17/2015 15:10:26 - Info bpbkar (pid=25067) 40000 entries sent to bpdbm
	11/17/2015 15:10:31 - Info bpbkar (pid=25067) 45000 entries sent to bpdbm
	11/17/2015 15:10:42 - Info bpbkar (pid=25067) 50000 entries sent to bpdbm
	11/17/2015 15:10:44 - Info bpbkar (pid=25067) 55000 entries sent to bpdbm
	11/17/2015 15:10:47 - Info bpbkar (pid=25067) 60000 entries sent to bpdbm
	11/17/2015 15:10:49 - Info bpbkar (pid=25067) 65000 entries sent to bpdbm
	11/17/2015 15:10:53 - Info bpbkar (pid=25067) 70000 entries sent to bpdbm
	11/17/2015 15:10:57 - Info bpbkar (pid=25067) 75000 entries sent to bpdbm
	11/17/2015 15:11:11 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/usr/openv/var/vnetd/bpcd.uds] is a socket special file. Skipping
	11/17/2015 15:11:11 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/usr/openv/var/vnetd/terminate_bpcd.uds] is a socket special file. Skipping
	11/17/2015 15:11:11 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/usr/openv/var/vnetd/terminate_vnetd.uds] is a socket special file. Skipping
	11/17/2015 15:11:13 - Info bpbkar (pid=25067) 80000 entries sent to bpdbm
	11/17/2015 15:11:16 - Info bpbkar (pid=25067) 85000 entries sent to bpdbm
	11/17/2015 15:11:18 - Info bpbkar (pid=25067) 90000 entries sent to bpdbm
	11/17/2015 15:11:21 - Info bpbkar (pid=25067) 95000 entries sent to bpdbm
	11/17/2015 15:11:26 - Info bpbkar (pid=25067) 100000 entries sent to bpdbm
	11/17/2015 15:11:33 - Info bpbkar (pid=25067) 105000 entries sent to bpdbm
	11/17/2015 15:11:34 - Info bpbkar (pid=25067) 110000 entries sent to bpdbm
	11/17/2015 15:11:35 - Info bpbkar (pid=25067) 115000 entries sent to bpdbm
	11/17/2015 15:11:36 - Info bpbkar (pid=25067) 120000 entries sent to bpdbm
	11/17/2015 15:11:37 - Info bpbkar (pid=25067) 125000 entries sent to bpdbm
	11/17/2015 15:11:39 - Info bpbkar (pid=25067) 130000 entries sent to bpdbm
	11/17/2015 15:11:41 - Info bpbkar (pid=25067) 135000 entries sent to bpdbm
	11/17/2015 15:11:43 - Info bpbkar (pid=25067) 140000 entries sent to bpdbm
	11/17/2015 15:11:44 - Info bpbkar (pid=25067) 145000 entries sent to bpdbm
	11/17/2015 15:11:45 - Info bpbkar (pid=25067) 150000 entries sent to bpdbm
	11/17/2015 15:11:47 - Info bpbkar (pid=25067) 155000 entries sent to bpdbm
	11/17/2015 15:11:49 - Info bpbkar (pid=25067) 160000 entries sent to bpdbm
	11/17/2015 15:11:50 - Info bpbkar (pid=25067) 165000 entries sent to bpdbm
	11/17/2015 15:11:50 - Info bpbkar (pid=25067) 170000 entries sent to bpdbm
	11/17/2015 15:11:52 - Info bpbkar (pid=25067) 175000 entries sent to bpdbm
	11/17/2015 15:11:55 - Info bpbkar (pid=25067) 180000 entries sent to bpdbm
	11/17/2015 15:11:59 - Info bpbkar (pid=25067) 185000 entries sent to bpdbm
	11/17/2015 15:12:00 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/var/run] is in a different file system from [/]. Skipping
	11/17/2015 15:12:00 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/var/sadm/install/.door] is a door file. Skipping
	11/17/2015 15:12:05 - Info bpbkar (pid=25067) 190000 entries sent to bpdbm
	11/17/2015 15:12:11 - Info bpbkar (pid=25067) 195000 entries sent to bpdbm
	11/17/2015 15:12:29 - Info bpbkar (pid=25067) 200000 entries sent to bpdbm
	11/17/2015 15:12:40 - Info bpbkar (pid=25067) 205000 entries sent to bpdbm
	11/17/2015 15:12:46 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/var/tmp/om] is on file system type NFS. Skipping
	11/17/2015 15:12:46 - Info bpbrm (pid=7012) from client vnmhnned1-bkup: TRV - [/vol] is on file system type NFS. Skipping
	11/17/2015 15:12:46 - Info bptm (pid=7035) waited for full buffer 5275 times, delayed 8428 times
	11/17/2015 15:12:47 - Error bpbrm (pid=7012) db_flist_complete failed: file read failed (13) vnmhnned1-bkup vnmhnned1-bkup_FILES 1 1447747688

&nbsp;

bptm logs :--&gt;&nbsp;See attached

bpbrm logs :--&gt; See attached

bpbkar logs :--&gt; See attached

&nbsp;

Please help in finding solution

&nbsp;

Regards

S.

&nbsp;

marianne · Answer

I have move the logs to attachment as this makes the post easier to read.

Please give us as much info as possible.

You have selected 7.5 as NBU version - please tell us version and patch level on all NBU components - master, media server and client.

OS - Solaris (or other OS) version on master, media server and client.

Info about this failure:

Is this the only client failing?
	Incr and Full backups failing or only Incr?

What is in Backup Selection?
	If ALL_LOCAL_DRIVES - have you selected 'Allow multiple data streams' in policy attributes?
	What are backup results with and without&nbsp;'Allow multiple data streams'?

We see this in bpbkar log:

WRN - Old TIR file /usr/openv/netbackup/tir_info//NetBackup_file_info.vnmhnned1-bkup_FILES is missing. Backing up everything in /

Does this mean that you have TIR enabled in the policy?
	Have you tried without TIR?

What are KeepAlive TCP settings on the client and media server?

The bpbkar log that you have posted does not seem to be an actual bpbkar log.&nbsp;
	Please copy client's bpbkar log to bpbkar.txt and upload as File attachment.

symsonu · Answer

You have selected 7.5 as NBU version - please tell us version and patch level on all NBU components - master, media server and client.

&nbsp;

HARDWARE SOLARIS_X86
	VERSION NetBackup 7.5.0.4
	RELEASEDATE Sun Sep 16 11:43:30 CDT 2012
	BUILDNUMBER 20120916
	&nbsp;

&nbsp;

OS - Solaris (or other OS) version on master, media server and client.

Solaris 10

Info about this failure:

Is this the only client failing?

&nbsp;

All Policies failing with error code 42 except one ... and that very one has TIR disabled

Incr and Full backups failing or only Incr?

&nbsp;

Both

What is in Backup Selection?
	If ALL_LOCAL_DRIVES - have you selected 'Allow multiple data streams' in policy attributes?
	What are backup results with and without 'Allow multiple data streams'?

&nbsp;

Yes , Allow multiple datastreams --checked

We see this in bpbkar log:

WRN - Old TIR file /usr/openv/netbackup/tir_info//NetBackup_file_info.vnmhnned1-bkup_FILES is missing. Backing up everything in /

Does this mean that you have TIR enabled in the policy?

Yes
	Have you tried without TIR?

I tried it now and&nbsp; backup is successful

What are KeepAlive TCP settings on the client and media server?

The bpbkar log that you have posted does not seem to be an actual bpbkar log.
	Please copy client's bpbkar log to bpbkar.txt and upload as File attachment

&nbsp;

Can you help me with the reason why policy is failing if we are selecting TIR ?

marianne · Answer

I cannot say why backup is failing with TIR enabled.

Do you really need TIR?

Google found a couple of TNs and forum posts. See if any of these helps:

http://www.veritas.com/docs/000041650&nbsp;

http://www.veritas.com/docs/000022618&nbsp;

https://www-secure.symantec.com/connect/forums/old-tir-info-file-missing-client-can-it-be-restored-or-recreated

Forum Discussion

backup job failing with erro code 42

3 Replies

Related Content

VM backup failing with (11) system call failed

Backup failed

Catalog Backup Failing with Error code 9202

Backup jobs failed

vCenter backup fail