12-26-2013 08:27 PM
Hello All,
Till last month we configured catalog backup to disk STU ("Network Hard disk" attached to master server), now we changed catalog to media manager STU, and the actual network drive server was decommisioned and now the "Image cleanup jobs are failing with 83 status because they are not able to cleanup the jobs. I want to know what else can we do to fix this issue apart from daily failure of cleanup job.
Master serv:-2003/NBU 7.0
Failed Job Details:-
12/26/2013 11:26:42 PM - Info bpdbm(pid=7560) image catalog cleanup
12/26/2013 11:26:42 PM - Info bpdbm(pid=7560) Cleaning up tables in the relational database
12/26/2013 11:26:42 PM - Info bpdbm(pid=7560) deleting images which expire before Thu Dec 26 23:26:42 2013 (1388080602)
12/26/2013 11:26:42 PM - Info bpdbm(pid=7560) processing client GSPTSSVR
12/26/2013 11:26:43 PM - Info bpdbm(pid=7560) processing client IE03NAS004
12/26/2013 11:26:43 PM - Info bpdbm(pid=7560) processing client IE03SR2K302926
12/26/2013 11:26:43 PM - Info bpdbm(pid=7560) processing client IE03SR2K303283
12/26/2013 11:26:43 PM - Info bpdbm(pid=7560) processing client IE03SR2K315045
12/26/2013 11:26:43 PM - Info bpdbm(pid=7560) processing client IE03SV2K313387
12/26/2013 11:26:44 PM - Info bpdbm(pid=7560) processing client IE03W16288
12/26/2013 11:26:44 PM - Info bpdbm(pid=7560) processing client IE03W1RMSD1S
12/26/2013 11:26:44 PM - Info bpdbm(pid=7560) processing client IE03WJQMSD1S
12/26/2013 11:26:46 PM - Info bpdbm(pid=7560) processing client IE67WHBK8R1S
12/26/2013 11:26:46 PM - Info bpdbm(pid=7560) processing client IE67WHBYQG1S
12/26/2013 11:26:46 PM - Info bpdbm(pid=7560) processing client ie03nas005
12/26/2013 11:26:52 PM - Info bpdbm(pid=7560) processing client ie03ntftps
12/26/2013 11:26:53 PM - Info bpdbm(pid=7560) processing client ie03sr2k013464
12/26/2013 11:26:53 PM - Info bpdbm(pid=7560) processing client ie03sr2k301139
12/26/2013 11:26:53 PM - Info bpdbm(pid=7560) processing client ie03sr2k312539
12/26/2013 11:26:53 PM - Info bpdbm(pid=7560) processing client ie03sr2k314023
12/26/2013 11:26:53 PM - Info bpdbm(pid=7560) processing client ie03w5rmr5bs
12/26/2013 11:26:54 PM - Info bpdbm(pid=7560) processing client ie03wbjb9vq1
12/26/2013 11:27:00 PM - Info bpdbm(pid=7560) processing client ie67sr2k30tmwq1
12/26/2013 11:27:01 PM - Info bpdbm(pid=7560) processing client ie67vw0001
12/26/2013 11:27:02 PM - Info bpdbm(pid=7560) processing client ie67vw0002
12/26/2013 11:27:04 PM - Info bpdbm(pid=7560) processing client ie67w3j7s8r1
12/26/2013 11:27:05 PM - Info bpdbm(pid=7560) processing client ie67w9yrrt1s
12/26/2013 11:27:05 PM - Info bpdbm(pid=7560) processing client ie67wjmb8f2sv2
12/26/2013 11:27:05 PM - Info bpdbm(pid=7560) deleted 26 expired records, compressed 0, tir removed 2, deleted 0 expired copies
12/26/2013 11:27:05 PM - Info nbdelete(pid=4380) deleting expired images. Media Server: ie03nas004 Media: H:\CatalogBackup
12/26/2013 11:27:06 PM - started process bpdm (2876)
12/26/2013 11:27:06 PM - Critical bpdm(pid=2876) sts_get_lsu_prop_byname on LSU H:\CatalogBackup failed: 2060013 no more entries
12/26/2013 11:27:06 PM - Critical bpdm(pid=2876) Invalid storage device: H:\CatalogBackup no more entries
12/26/2013 11:27:06 PM - Critical bpdm(pid=2876) failure to open disk at path H:\CatalogBackup: plug-in reports error 2060013 no more entries
12/26/2013 11:27:06 PM - Error bpdm(pid=2876) volume H:\CatalogBackup does not exist or is not available.
media open error(83)
Solved! Go to Solution.
12-27-2013 12:34 AM
nbdelete -allvolumes -force
If that doesn't clear it you will have to raise a Symantec case to get the images removed.
12-26-2013 09:02 PM
12/26/2013 11:27:06 PM - Critical bpdm(pid=2876) sts_get_lsu_prop_byname on LSU H:\CatalogBackup failed: 2060013 no more entries
12/26/2013 11:27:06 PM - Critical bpdm(pid=2876) Invalid storage device: H:\CatalogBackup no more entries
12/26/2013 11:27:06 PM - Critical bpdm(pid=2876) failure to open disk at path H:\CatalogBackup: plug-in reports error 2060013 no more entries
12/26/2013 11:27:06 PM - Error bpdm(pid=2876) volume H:\CatalogBackup does not exist or is not available.
media open error(83)
does H:\CatalogBackup this the catalog backup location ?
when did you have the last successfull catalog backup?
12-26-2013 09:54 PM
Hi Nagalla,
H:\CatalogBackup was the previous catalog backup location, i.e previously we had catalog backup on Disk( Network disk mapped to NBU Master server) but now the network disk was disabled becoz the server decom. but now we configured catalog backup to tape. and we had succesfull catalog backup yesterday also.
12-26-2013 09:58 PM
Here are the succesfull catalog job details
12-26-2013 10:09 PM
does the backup on tape is Full backup?
12-26-2013 10:31 PM
No its incremental, catalog full backup will run on every friday in my envir...
12-26-2013 11:29 PM
i was just trying to check, if you have the full catalog backup on Tape or not.. might not be yesterday one..
and it looks like the H:\CatalogBackup is not removed from the DB
check this
http://www.symantec.com/business/support/index?page=content&id=TECH62005
http://www.symantec.com/business/support/index?page=content&id=TECH70275
run this command
nbdelete -allvolumes -force
12-27-2013 12:17 AM
Hello Nagalla,
yes we had full catalog backup on tape,
iorder to remove the "H:\CatalogBackup" from DB is there any simple way?
12-27-2013 12:34 AM
nbdelete -allvolumes -force
If that doesn't clear it you will have to raise a Symantec case to get the images removed.
12-27-2013 12:37 AM
agreed with Revaroo...
try the command nbdelete listed in above post...
12-27-2013 01:25 AM
Hi Revaroo,
thanks for your advice. i want to know if i execute "nbdelete " it wont effect present catalog file right?
and i need to execute in admincmd right?
12-27-2013 01:36 AM
it only removes the deletes fragments... and its located on /usr/openv/netbackup/bin/admincmd/
and no impact to the the existing images..
12-27-2013 03:34 AM
or more accurately in this case, because the deleted fragments are not available, the nbdelete -allvolumes force command will go ahead and cleanup the database without deleteing the actual fragments.