|
Solaris 7? Sheesh...
SCSI errors also cause status 84 messages - basically anything that causes a media error will result in an 84. I've seen it when our SAN ISLs generated errors (too fast for the media and distance) and we generated SCSI errors.
Check the non-NetBackup logs for possible errors as well.
..../Ed
On Tue, Apr 8, 2008 at 6:14 PM, stv006 < netbackup-forum AT backupcentral DOT com> wrote:
I have an issue with bpbackupdb ending with status 84. Already tried to do the backup to other tapes, but all ended with 84.
NetBackup version is NetBackup-Solaris7 5.1MP6
No other jobs end with this error. Here is what I got from the bpdbjobs:
# bpdbjobs -jobid 574876
JobID Type State Status Policy Client Schedule Kilobytes Started Ended Dest Media Dest StUni Started
574876 Cata Done 84 ott-nb3 04/04/08 17:35 04/04/08 21:54 04/04/08 17:35
# bpdbjobs -jobid 574876 -all_columns
574876,6,3,84,,,ott-nb3,,1207344945,0000015532,1207360477,,1,,,,,100,15392,root,,,,,,ott-nb3.cisco.com,,,,,,0,1,15392,,,1207344945,0000015532,1207360477,84,media write error,10,04/04/08 17:35:45 - begin Catalog Backup operation,04/04/08 17:35:45 - mounting B25101,04/04/08 17:35:45 - started process bptm (15394),04/04/08 17:35:45 - started process bptm (15394),04/04/08 17:35:45 - mounting B25101,04/04/08 17:36:55 - mounted; mount time: 000:01:10,04/04/08 21:54:35 - Error bpbackupdb(pid=15392) cannot write image to /tmp/sync_B25101\, Error 0,04/04/08 21:54:37 - started process bptm (25275),04/04/08 21:54:37 - end Catalog Backup operation; operation time: 004:18:52,04/04/08 21:54:37 - Error bpbackupdb(pid=15392) NB database backup to media id B25101 FAILED,0,0,,,,,,,,,,,,,,,,,,,,,
#
Can be anything related with the message cannot write image to /tmp/sync_B25101?
--
Ed Wilts, Mounds View, MN, USA
mailto:ewilts AT ewilts DOT org
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
