cancel
Showing results for 
Search instead for 
Did you mean: 

File Write Failed (14)

L_BR
Level 5

Greetings,

Environment:

Master Server: Windows 2K8 R2 - Netbackup 7.6.1.1

Media Server: Windows 2K8 R2 - Netbackup 7.6.1.1

Client: AIX 7.1 - Netbackup 7.6.1.2

Problem: We have been running DB2 backups (using Templates) for a few weeks now. We started noticing that the instances were failing to back up. When we asked our DB2 admin to recreate the templates after troubleshooting, he experienced the following error when trying to log in to the Java Console: file write failed (14). We asked him to run the application as an Admin and he still got the same problem. I tried to increase the logging levels on the client through client properties and got the same error when clicking Apply or Ok after setting the levels higher. Any ideas or advice?

 

If need be, here is the Detailed Status of the Parent job, a child job is never started because it fails.

2015/07/17 06:10:24 AM - Info nbjm(pid=11504) starting backup job (jobid=944862) for client sapqdb1.sap.shoprite.co.za, policy qa_sapqdb1_vepqdb_epq_db2, schedule full  
2015/07/17 06:10:24 AM - Info nbjm(pid=11504) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=944862, request id:{58D8D43C-19E7-492E-AA39-49E4CFBF1B63})  
2015/07/17 06:10:24 AM - requesting resource m2_ho4_norep_med7
2015/07/17 06:10:24 AM - requesting resource nbuprodmst2.shoprite.co.za.NBU_CLIENT.MAXJOBS.sapqdb1.sap.shoprite.co.za
2015/07/17 06:10:24 AM - requesting resource nbuprodmst2.shoprite.co.za.NBU_POLICY.MAXJOBS.qa_sapqdb1_vepqdb_epq_db2
2015/07/17 06:10:24 AM - granted resource nbuprodmst2.shoprite.co.za.NBU_CLIENT.MAXJOBS.sapqdb1.sap.shoprite.co.za
2015/07/17 06:10:24 AM - granted resource nbuprodmst2.shoprite.co.za.NBU_POLICY.MAXJOBS.qa_sapqdb1_vepqdb_epq_db2
2015/07/17 06:10:24 AM - granted resource m2_ho4_norep_med7
2015/07/17 06:10:24 AM - estimated 0 Kbytes needed
2015/07/17 06:10:24 AM - Info nbjm(pid=11504) started backup (backupid=sapqdb1.sap.shoprite.co.za_1437106224) job for client sapqdb1.sap.shoprite.co.za, policy qa_sapqdb1_vepqdb_epq_db2, schedule full on storage unit m2_ho4_norep_med7
2015/07/17 06:10:26 AM - started process bpbrm (8212)
2015/07/17 06:10:28 AM - Info bpbrm(pid=8212) sapqdb1.sap.shoprite.co.za is the host to backup data from     
2015/07/17 06:10:28 AM - Info bpbrm(pid=8212) reading file list for client        
2015/07/17 06:10:28 AM - connecting
2015/07/17 06:10:31 AM - Info bpbrm(pid=8212) starting bphdb on client         
2015/07/17 06:10:31 AM - Info bphdb(pid=27721800) Backup started           
2015/07/17 06:10:31 AM - connected; connect time: 0:00:03
2015/07/17 06:10:32 AM - Info bphdb(pid=27721800) Processing 3a44424e414d453a6462326570713a4442484f4d453a2f6462322f6462326570713a44424e45544e414d453a:DBTEMPLATENAME:db2epq.tpl           
2015/07/17 06:10:32 AM - Info bphdb(pid=27721800) Waiting for the child status        
2015/07/17 06:10:33 AM - Error bpbrm(pid=8212) from client sapqdb1.sap.shoprite.co.za: ERR - Script exited with status = 1 <the requested operation was partially successful>
2015/07/17 06:10:34 AM - Error bpbrm(pid=8212) from client sapqdb1.sap.shoprite.co.za: ERR - bphdb exit status = 6: the backup failed to back up the requested files
2015/07/17 06:10:36 AM - Info bphdb(pid=27721800) done. status: 6: the backup failed to back up the requested files
2015/07/17 06:10:36 AM - end writing
the backup failed to back up the requested files (6)

 

I got the following log files from the DB2 Admin

bphdb - Provides same error as Detailed Status.

bpbrm - No log file created (folder has been created)

dbclient - No log file created (folder has been created)

1 ACCEPTED SOLUTION

Accepted Solutions

L_BR
Level 5

Not necessarily a "resolution", but uninstalling and reinstalling Netbackup on the client seems to have resolved the issue. So far 2 of the instances i've tested are now writing.

View solution in original post

1 REPLY 1

L_BR
Level 5

Not necessarily a "resolution", but uninstalling and reinstalling Netbackup on the client seems to have resolved the issue. So far 2 of the instances i've tested are now writing.