cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Catalog backup is failing with code status 42

07/26/2016 23:57:38 - Info nbjm (pid=4062) starting backup job (jobid=1398341) for client fclbk05, policy CATALOG-DISK, schedule Full
07/26/2016 23:57:38 - Info nbjm (pid=4062) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1398341, request id:{6801F87C-53C7-11E6-B102-4D1E950FE5CC})
07/26/2016 23:57:38 - requesting resource data01-catalog
07/26/2016 23:57:38 - requesting resource fclbk05.NBU_CLIENT.MAXJOBS.fclbk05
07/26/2016 23:57:38 - requesting resource fclbk05.NBU_POLICY.MAXJOBS.CATALOG-DISK
07/26/2016 23:57:39 - Info bpbrm (pid=29818) fclbk05 is the host to backup data from
07/26/2016 23:57:39 - Info bpbrm (pid=29818) reading file list from client
07/26/2016 23:57:39 - Info bpbrm (pid=29818) starting bpbkar on client
07/26/2016 23:57:39 - Info bpbkar (pid=29822) Backup started
07/26/2016 23:57:39 - Info bpbrm (pid=29818) bptm pid: 29823
07/26/2016 23:57:39 - granted resource fclbk05.NBU_CLIENT.MAXJOBS.fclbk05
07/26/2016 23:57:39 - granted resource fclbk05.NBU_POLICY.MAXJOBS.CATALOG-DISK
07/26/2016 23:57:39 - granted resource MediaID=@aaaab;Path=/data01/backup/catalog;MediaServer=fclbk05
07/26/2016 23:57:39 - granted resource data01-catalog
07/26/2016 23:57:39 - estimated 0 kbytes needed
07/26/2016 23:57:39 - Info nbjm (pid=4062) started backup (backupid=fclbk05_1469602659) job for client fclbk05, policy CATALOG-DISK, schedule Full on storage unit data01-catalog
07/26/2016 23:57:39 - started process bpbrm (pid=29818)
07/26/2016 23:57:39 - connecting
07/26/2016 23:57:39 - connected; connect time: 0:00:00
07/26/2016 23:57:40 - Info bptm (pid=29823) start
07/26/2016 23:57:40 - Info bptm (pid=29823) using 262144 data buffer size
07/26/2016 23:57:40 - Info bptm (pid=29823) using 128 data buffers
07/26/2016 23:57:40 - Info bptm (pid=29823) start backup
07/26/2016 23:57:40 - begin writing
07/27/2016 01:22:49 - Warning bpbrm (pid=29818) from client fclbk05: WRN - /usr/openv/netbackup/db/error/daily_messages.log is only being backed up as a symbolic link
07/27/2016 01:22:49 - Info bpbrm (pid=29818) from client fclbk05: TRV - Cannot process path [/usr/openv/netbackup/db/error/log_1465714800]: [No such file or directory]. Skipping
07/27/2016 01:23:03 - Info bpbkar (pid=29822) bpbkar waited 673 times for empty buffer, delayed 744630 times
07/27/2016 01:23:03 - Info bptm (pid=29823) waited for full buffer 139646 times, delayed 237351 times
07/27/2016 01:31:23 - Error bptm (pid=29823) get_string() failed, Input/output error (5), premature end of file encountered
07/27/2016 01:31:23 - Info bptm (pid=29823) EXITING with status 42 <----------
07/27/2016 01:35:28 - Info bpbkar (pid=29822) done. status: 42: network read failed
07/27/2016 01:35:28 - end writing; write time: 1:37:48
network read failed (42)

Tags (2)
3 Replies
Highlighted

Re: Catalog backup is failing with code status 42

Could someone please let us know how can we fix this issue >

Tags (2)
Highlighted

Re: Catalog backup is failing with code status 42

When last did a full catalog backup succeed? 
Have you tried to schedule the catalog backup at another time that does not cross midnight?

There is no quick fix for this error. 
I found 3 references to catalog backup failing with status 42 but none of those seem relevant. 
(one was incremental backup failing and was fixed by running a full, another was about catalog backup done by a media server and the 3rd was for a Windows master with some OS limitation)

You will need to look into logs to find the reason for this error.

Level 3 logs may be sufficient, but if you log a Support call with Veritas, they will request level 5 logs.

Since the master server is also the media server, all of these log folders must be created on the master server:
bpdbm (restart NBU after creating the folder)
bptm
bpbrm
bpbkar

 

Highlighted

Re: Catalog backup is failing with code status 42

dear,

most network failures should be worked through capturing logs. catalog backup is local to the master server, hence logs should be from master.

Please share the logs which Marianne has asked. Thanks.