cancel
Showing results for 
Search instead for 
Did you mean: 

Catalog Backup Error Status 14

Hi everyone, I am having issues with our Catalog backup after we upgraded to 7.6.1.1. This environment is a simple 5220 Appliance which acts as our Master/Media server connected to an IBM library on the back end. When executing our Catalog backup everything seems to complete successfully except for the dr file save part of the process. I have verified that I can browse to the dr_file directory and have remapped with credentials successfully. Tried pointing dr file save to another directory which still failed, and also verified that there is plenty of space on the drive to complete. Not sure what else to try. I have included the job details below.

Detailed Status

 

8/19/2015 9:24:11 AM - Info nbjm(pid=11786) starting backup job (jobid=186802) for client XXXXXXXXXXX, policy Catalog-Backup, schedule Catalog-Backup_Full  
8/19/2015 9:24:11 AM - Info nbjm(pid=11786) requesting CATALOG_BACKUP_RESOURCE resources from RB for backup job (jobid=186802, request id:{941653FA-4675-11E5-8AFF-F1C3347D7AAD})  
8/19/2015 9:24:11 AM - requesting resource XXXXXXXXXXX.NBU_CATALOG.MAXJOBS
8/19/2015 9:24:11 AM - granted resource XXXXXXXXXXX.NBU_CATALOG.MAXJOBS
8/19/2015 9:24:11 AM - estimated 0 Kbytes needed
8/19/2015 9:24:11 AM - begin Parent Job
8/19/2015 9:24:11 AM - begin Catalog Backup, Start Notify Script
8/19/2015 9:24:11 AM - Info RUNCMD(pid=25799) started            
8/19/2015 9:24:11 AM - Info RUNCMD(pid=25799) exiting with status: 0         
Status 0
8/19/2015 9:24:11 AM - end Catalog Backup, Start Notify Script; elapsed time: 0:00:00
8/19/2015 9:24:11 AM - begin Catalog Backup, DBM Query
8/19/2015 9:29:26 AM - Error bpdbm(pid=25803) Unable to save disaster recovery information to /advdisk/dr_file: file write failed (14) 
Status 14
8/19/2015 9:29:27 AM - end Catalog Backup, DBM Query; elapsed time: 0:05:16
8/19/2015 9:29:27 AM - begin Catalog Backup, Stop On Error
Status 0
8/19/2015 9:29:27 AM - end Catalog Backup, Stop On Error; elapsed time: 0:00:00
8/19/2015 9:29:27 AM - begin Catalog Backup, End Notify Script
8/19/2015 9:29:27 AM - Info RUNCMD(pid=26607) started            
8/19/2015 9:29:27 AM - Info RUNCMD(pid=26607) exiting with status: 0         
Status 0
8/19/2015 9:29:27 AM - end Catalog Backup, End Notify Script; elapsed time: 0:00:00
Status 14
8/19/2015 9:29:27 AM - end Parent Job; elapsed time: 0:05:16
file write failed(14)

2 Replies

Perhaps try saving the DR

Perhaps try saving the DR file somewhere like /home/maintenance/dr_file ?  Does that work?  Perhaps permissions have changed within the 'appliance' as a black box, and you're simply no longer allowed to do what you used to do.

As per the best practice, the

As per the best practice, the DR file should be kept on  an alternate server so that it can be used while performing DR. 

You can mount a NFS share and write to it.