Spurious Alerts following Appliance Upgrade to 2.7.2
I have recently upgraded a number of 5230 Appliances to 2.7.2, and whilst all appear to be functioning as expected we are getting numerous alerts relating to disk failures which are 'false'. I am wondering whether there is a BIOS issue here (mismatch) ? Two questions: 1. How can I display the current BIOS level without rebooting the appliance ? 2. Is there a required BIOS update to be applied 'outside' of the regular software/firmware package used for 2.7.2 ? Thanks, AJ.
netbackup unable to resolve hostname, no hostname alias added to pem name manager.
Hi, I see the below error on my problems report: netbackup unable to resolve hostname <hostname>, no hostname alias added to pem name manager. Now there's about 16 of these servers and they have all been decommissioned and they are not associated with any policy and they are not under client's host properties on the GUI. Upon searching under the /usr/openv/netbackup/db/client directory, all 16 of these client folders are still in there. Is it OK to just remove/delete these client folders on this directory? Or is there another way of getting rid of these error? Regards
Catalog Backup Error Status 14
Hi everyone, I am having issues with our Catalog backup after weupgraded to 7.6.1.1. Thisenvironment 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)