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

network read failed(42)

Hi All,

Full catalog backup(f:\catalog drive assigned from VMAX storage array) completed fine on last sunday. then on monday we assigned E drive from Pure and did robocopy for F drive to E drive. All catalog data moved to E drive on Monday.

Then i chanded drive lettrs F drive into G drive. And, E drive to F drive(now my F:\catalog drive is from Pure storage).

When diff catalog backup started on Monday it failed with 42.

I am now running Full catalog backup and dont know if it will complete complete. it will take another 6 hours to confirm.

May i know what caused the failure and what i need to do?

 

Thank you in advance.

 

 

Tags (2)
5 Replies
Highlighted

Re: network read failed(42)

You would need to give us more inputs.. how many streams did the catalog backup generate and which one failed with status 42.. all or just the last stream for image db..

complete job details would also be helpful..

Your selections says windows 2003 so probably you are running an old unsupported nbu version..

Usually catalog backup failure troubleshooting requires bpdbm logs but ofcourse depends on which part of the job failed in your case.. if you have a different media server in place it could also be more of a connectivity issue from master to media or vice versa
Highlighted

Re: network read failed(42)

I am missing something here - 

What exactly is on f:\catalog ?
The storage unit where Catalog backup is written?
Or NBU image and/or other parts of the NBU Catalogs?

If NBU Catalogs, did you stop NBU while copying contents to new location?

To know what caused the error, you firstly need to see which NBU process reported the error (in Job details) and check the log(s).
Legacy logging is not enabled by default - folders need to be created under ...NetBackup\logs.
All of these processes are involved in a catalog backup:
bpdbm and bpbkar on the master server (NBU needs to be restarted to enable bpdbm log)
bpbrm and bptm on the media server.
Default logging level of 0 will probably not log sufficient info. Level 3 should be enough.

Re: network read failed(42)

 what about the other jobs ( Non catalog backup) ? Are they completing fine ?

 

DeepS

Highlighted

Re: network read failed(42)

Hi All,

Backup completed by doing Full backup Prior to Diff Backup. 1 out of 3 streams failed and all otrher backups also failed.

Sorry for "f:\catalog"--> its my catalog backup related DR path in drive F along with my image data base.

Dont know whats the issue and how can full backup fixed this. Below is the detailed status on error.

But, i am receving alert mails from my opscenter like "Available Catalog Space below 40 GB" from full backup running day onwards. my catalog backup and image data bse stays in F Drive which had 700 GB free space out of 2 TB.  I will open new thread for that.

Details Status:

Mar 13, 2018 10:59:55 AM - Info nbjm (pid=4876) starting backup job (jobid=670024) for client edc-bkp01, policy Catalog, schedule Diff
Mar 13, 2018 10:59:55 AM - Info nbjm (pid=4876) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=670024, request id:{11B8724C-8097-45A4-AED7-8A38CBF0DB94})
Mar 13, 2018 10:59:55 AM - requesting resource LTO5_Media_Manager
Mar 13, 2018 10:59:55 AM - requesting resource edc-bkp01.NBU_CLIENT.MAXJOBS.edc-bkp01
Mar 13, 2018 10:59:55 AM - requesting resource edc-bkp01.NBU_POLICY.MAXJOBS.Catalog
Mar 13, 2018 10:59:55 AM - granted resource  edc-bkp01.NBU_CLIENT.MAXJOBS.edc-bkp01
Mar 13, 2018 10:59:55 AM - granted resource  edc-bkp01.NBU_POLICY.MAXJOBS.Catalog
Mar 13, 2018 10:59:55 AM - granted resource  000697
Mar 13, 2018 10:59:55 AM - granted resource  HP.ULTRIUM5-SCSI.007
Mar 13, 2018 10:59:55 AM - granted resource  edc-bkp01-hcart-robot-tld-0
Mar 13, 2018 10:59:55 AM - estimated 0 kbytes needed
Mar 13, 2018 10:59:55 AM - Info nbjm (pid=4876) started backup (backupid=edc-bkp01_1520956795) job for client edc-bkp01, policy Catalog, schedule Diff on storage unit edc-bkp01-hcart-robot-tld-0
Mar 13, 2018 10:59:55 AM - Info bpbrm (pid=11552) edc-bkp01 is the host to backup data from
Mar 13, 2018 10:59:55 AM - Info bpbrm (pid=11552) reading file list for client
Mar 13, 2018 10:59:55 AM - started process bpbrm (pid=11552)
Mar 13, 2018 10:59:55 AM - connecting
Mar 13, 2018 10:59:56 AM - Info bpbrm (pid=11552) starting bpbkar32 on client
Mar 13, 2018 10:59:56 AM - Info bpbkar32 (pid=10684) Backup started
Mar 13, 2018 10:59:56 AM - Info bpbkar32 (pid=10684) change time comparison:<disabled>
Mar 13, 2018 10:59:56 AM - Info bpbkar32 (pid=10684) archive bit processing:<enabled>
Mar 13, 2018 10:59:56 AM - Info bptm (pid=5116) start
Mar 13, 2018 10:59:56 AM - Info bptm (pid=5116) using 65536 data buffer size
Mar 13, 2018 10:59:56 AM - Info bptm (pid=5116) setting receive network buffer to 263168 bytes
Mar 13, 2018 10:59:56 AM - Info bptm (pid=5116) using 32 data buffers
Mar 13, 2018 10:59:56 AM - Info bptm (pid=5116) start backup
Mar 13, 2018 10:59:56 AM - Info bptm (pid=5116) Waiting for mount of media id 000697 (copy 1) on server edc-bkp01.
Mar 13, 2018 10:59:56 AM - connected; connect time: 0:00:00
Mar 13, 2018 10:59:56 AM - mounting 000697
Mar 13, 2018 11:00:42 AM - Info bptm (pid=5116) media id 000697 mounted on drive index 8, drivepath {6,0,2,0}, drivename HP.ULTRIUM5-SCSI.007, copy 1
Mar 13, 2018 11:00:42 AM - mounted 000697; mount time: 0:00:46
Mar 13, 2018 11:00:48 AM - positioning 000697 to file 26
Mar 13, 2018 11:02:32 AM - positioned 000697; position time: 0:01:44
Mar 13, 2018 11:02:32 AM - begin writing
Mar 13, 2018 11:08:51 AM - Info bpbkar32 (pid=10684) bpbkar waited 140 times for empty buffer, delayed 144 times.
Mar 13, 2018 11:08:51 AM - Info bptm (pid=5116) waited for full buffer 661 times, delayed 24081 times
Mar 13, 2018 11:08:53 AM - Error bpbrm (pid=11552) db_flist_complete failed: No dotf file (2506) edc-bkp01 Catalog 1 1520956795
Mar 13, 2018 11:17:12 AM - Error bptm (pid=5116) get_string() failed, Broken pipe (32), premature end of file encountered
Mar 13, 2018 11:17:12 AM - Info bptm (pid=5116) EXITING with status 42 <----------
Mar 13, 2018 11:17:16 AM - Info bpbkar32 (pid=10684) done. status: 42: network read failed
Mar 13, 2018 11:17:16 AM - end writing; write time: 0:14:44
network read failed  (42)

 

Highlighted

Re: network read failed(42)

Did you shutdown NBU completely when you copied drive content to new volume?
If not, then you probably copied files that were in inconsistent state or missed changes after the copy.

This is the error:

db_flist_complete failed: No dotf file

There is information in the image header (located in EMM db) for which there is no .f file in the images folder structure. 

You will need level 3 or higher bpbrm and bpdbm logs for image details.

PS: 
NOT a good idea to have your image db and DR-file on the same drive letter.
How will you recover if you lose the entire volume?