Highlighted

Catalog backup error : file read failed (13)

Hi We encounter this error on catalog backup.

04/02/2019 12:05:38 - Info nbjm (pid=7192) starting backup job (jobid=1020423) for client bdowcbs07, policy BDOWCBS07_Catalog, schedule full
04/02/2019 12:05:38 - Info nbjm (pid=7192) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1020423, request id:{FEB847B1-9502-4A9B-8D25-C9D8C33DE72D})
04/02/2019 12:05:38 - requesting resource bdowcbs10_stu
04/02/2019 12:05:38 - requesting resource bdowcbs07.NBU_CLIENT.MAXJOBS.bdowcbs07
04/02/2019 12:05:38 - requesting resource bdowcbs07.NBU_POLICY.MAXJOBS.BDOWCBS07_Catalog
04/02/2019 12:05:38 - granted resource bdowcbs07.NBU_CLIENT.MAXJOBS.bdowcbs07
04/02/2019 12:05:38 - granted resource bdowcbs07.NBU_POLICY.MAXJOBS.BDOWCBS07_Catalog
04/02/2019 12:05:38 - granted resource MediaID=@aaaaf; DiskVolume=PureDiskVolume; DiskPool=bdowcbs10_dp;Path=PureDiskVolume;StorageServer=bdowcbs10;MediaServer=bdowcbs10
04/02/2019 12:05:38 - granted resource bdowcbs10_stu
04/02/2019 12:05:39 - estimated 0 kbytes needed
04/02/2019 12:05:39 - Info nbjm (pid=7192) started backup (backupid=bdowcbs07_1554177938) job for client bdowcbs07, policy BDOWCBS07_Catalog, schedule full on storage unit bdowcbs10_stu
04/02/2019 12:05:41 - Info bpbrm (pid=14268) bdowcbs07 is the host to backup data from
04/02/2019 12:05:41 - Info bpbrm (pid=14268) reading file list for client 04/02/2019 12:05:41 - started process bpbrm (pid=14268)
04/02/2019 12:05:41 - connecting
04/02/2019 12:05:42 - Info bpbrm (pid=14268) starting bpbkar32 on client
04/02/2019 12:05:43 - Info bpbkar32 (pid=18980) Backup started
04/02/2019 12:05:43 - Info bpbkar32 (pid=18980) change time comparison:
04/02/2019 12:05:43 - Info bpbkar32 (pid=18980) archive bit processing:
04/02/2019 12:05:43 - Info bptm (pid=7568) start
04/02/2019 12:05:43 - Info bptm (pid=7568) using 262144 data buffer size
04/02/2019 12:05:43 - Info bptm (pid=7568) setting receive network buffer to 1049600 bytes
04/02/2019 12:05:43 - Info bptm (pid=7568) using 30 data buffers
04/02/2019 12:05:43 - connected; connect time: 0:00:00
04/02/2019 12:06:01 - Info bptm (pid=7568) start backup
04/02/2019 12:06:39 - Info bptm (pid=7568) backup child process is pid 13768.9404 04/02/2019 12:06:39 - Info bptm (pid=13768) start
04/02/2019 12:06:40 - begin writing 04/02/2019 14:33:02 - Info bptm (pid=7568) waited for full buffer 406313 times, delayed 460543 times
04/02/2019 14:34:07 - Info bptm (pid=7568) EXITING with status 0 <----------
04/02/2019 14:34:07 - Info bdowcbs10 (pid=7568) StorageServer=PureDisk:bdowcbs10; Report=PDDO Stats (multi-threaded stream used) for (bdowcbs10): scanned: 512850764 KB, CR sent: 1153015 KB, CR sent over FC: 0 KB, dedup: 99.8%, cache hits: 1451 (0.3%)
04/02/2019 14:34:07 - Info bpbrm (pid=14268) validating image for client bdowcbs07
04/02/2019 14:34:08 - Error bpbrm (pid=14268) db_IMAGE failed: file read failed (13)
04/02/2019 14:34:09 - Info bpbkar32 (pid=18980) done. status: 13: file read failed
04/02/2019 14:34:09 - end writing; write time: 2:27:29 file read failed (13)

Tags (2)
1 Solution

Accepted Solutions
Accepted Solution!

Re: Catalog backup error : file read failed (13)

Hi @jjimenez2 ,

Is there any specific reason for you to perform this catalog backup in MSDP? If I were you I do this backup to another place.

Take a look this TN NetBackup Catalog Backup

NBU-CATALOG.JPG

Hope this help.

Thiago

View solution in original post

2 Replies

Re: Catalog backup error : file read failed (13)

@jjimenez2 

I hope you don't mind - I have edited your post to add some <shift-CR>'s to have timestamps at the beginning of new line.

It seems that you are backing up the catalog to MSDP on a media server.
This adds a number of complications to the entire process - especially when it comes to catalog recovery. 

Is there any way that you can perhaps add local storage as basic disk to the master server for catalog backups?
This will ensure smooth backup process and problem-free catalog recovery. 

To get back to this failed backup - 
It seems that the backup actually completed the 'write' portion successfully: 

04/02/2019 14:34:07 - Info bptm (pid=7568) EXITING with status 0 <----------

but then the 'validation' portion failed :

04/02/2019 14:34:07 - Info bpbrm (pid=14268) validating image for client bdowcbs07 
04/02/2019 14:34:08 - Error bpbrm (pid=14268) db_IMAGE failed: file read failed (13)

So, we need bpbrm log on the media server as a start. bpbrm logging level should be set to 3 (please only set logging level to 5 if you want to log a Support call with Veritas). 
bpdbm log on the master server might also be helpful (depending on what we see in bpbrm). 
Please bear in mind that NBU needs to be restarted after creating bpdbm log directory. 

Accepted Solution!

Re: Catalog backup error : file read failed (13)

Hi @jjimenez2 ,

Is there any specific reason for you to perform this catalog backup in MSDP? If I were you I do this backup to another place.

Take a look this TN NetBackup Catalog Backup

NBU-CATALOG.JPG

Hope this help.

Thiago

View solution in original post