Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Update to catalog index (Catalog index database) failed.

Created: 27 Nov 2013 • Updated: 14 Jan 2014 | 22 comments
This issue has been solved. See solution.

I'm trying to catalog tape, but Catalog Job stays in running state and nothing happens.Following error message pops up in windows event log every 30 seconds.

Update to catalog index (Catalog index database) failed.
Reason:  E:\Symantec\Backup Exec\Catalogs\<SERVERNAME>\ PerformBulkInsert()
r:\honshu\1798.1300r\becat\catindex\dll\..\catdbupdatethread.cpp(501)
 

I have rebuilt indexes, but it didn't help.

What next? I have some critical data to restore..

Operating Systems:

Comments 22 CommentsJump to latest comment

pkh's picture

It could be that the Catalog directory has become corrupted.  Try creating a new Catalog directory

1) Stop all BE services

2) Rename existing Catalog directory under the BE installation directory to Catalog.old.

3) Create a new Catalog directory

4) Start all BE services

If you manage to catalog sucessfully with your new Catalog directory, you can merge your old Catalog directory to the new one by

1) Stop all BE services

2) Copy the files from the old Catalog directory to the new one

3) Start all BE services

 

villeah's picture

Unfortunately re-creating the catalog folder didn't help. I was able to catalog some media, but after a while the same error appeared in the application log.

pkh's picture

Do you have sufficient disk space on your drive for the catalogs?

villeah's picture

Yeah there is. I even moved the catalogs to larger partition, but I'm still not able to catalogue media.

villeah's picture

Now I was able to view the job log for the failed catalog operation

 

Completed status: Failed
Final error: 0xe0000900 - The requested media is not listed in the media index and could not be mounted. To add the media's catalog information to the disk-based catalogs, run an inventory operation on the media and resubmit the Catalog operation.
Final error category: Backup Media Errors

For additional information regarding this error refer to link V-79-57344-2304

.
.
.

CatalogThe media for sequence number 1 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 2 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 3 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 4 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 5 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 6 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 7 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 8 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 9 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 10 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 11 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 12 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 13 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 14 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 15 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 16 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 17 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 18 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 19 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 20 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 21 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 22 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 23 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 24 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 25 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 26 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 27 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 28 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 29 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 30 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 31 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 32 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 33 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 34 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 35 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 36 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 37 in this media family has not been inventoried.

No sets on this media may be cataloged.

The media for sequence number 38 in this media family has not been inventoried.

No sets on this media may be cataloged.

 

 

I have run the inventory job and inventory + catalog.

Should I try this next? https://www-secure.symantec.com/connect/forums/catalog-job-fails-following-disaster-recovery

pkh's picture

It appears that the tape you want to catalog belongs a big backup set which uses a lot of tapes.  To restore the entire backup set, you need to inventory the whole set of the tapes, no. 1 - 38, and then catalog the tapes in sequence, i.e. tape 1, followed by tape 2, etc.

If you don't have the entire set of tapes, then you can uncheck the the “Request all media in the sequence for catalog operations” option.

villeah's picture

I unchecked the “Request all media in the sequence for catalog operations” option.

Now the catalog job completes successfully, but no data gets catalogued. The job log says:

This backup set has already been cataloged.
This backup set may not contain any data.

Also the same error message still appears in event log.

I have also repaired the database, bebuilt indices, compact and aged database.

What next?

pkh's picture

Which software created these tapes and when?

pkh's picture

If you go to the Media tab, click on these tapes, do you see any backup sets?

How big is the backup set?  There are a lot of tapes involved.

villeah's picture

Yes I am able to see the backup set from which I want to restore data (Exchange mailbox items). The size is 190GB and it should fit in one tape.

The backup is Vcenter backup with GRT enabled, could that be an issue?

 

pkh's picture

I don't think the type of backup is the problem.

You should determine why you have such a big set of tapes for such a small backup set.  If you are forever appending to tapes, then this is a bad practice.  You should overwrite your tapes more frequently so that you have smaller families of tapes.

villeah's picture

This backup set is in monthly rotation, and tapes were overwritten when this backup job was executed. I duplicate the data to tapes once a week. Once in a month I will put the tape to vault for this kind of purposes.

Overwrite period is short, so that's why those big tape families wonders me.

pkh's picture

For the subsequent duplicate jobs, do they append or ovewrite tapes? How many tapes are involved each month?

MusSeth's picture

Please apply the latest backup exec service pack, create a new catalog folder as directed by PKH with options use storage based catalogs and request all media in sequence unchecked and create a new catalog job to catalog  a media and than check if data is visble

this cataloging method will take some time because backup exec will read data on tape and than will recreate the catalogs.

 

 

BackupDawg's picture

And if this standard fix doesnt help - what then?

 

thanks

D

BDawg

villeah's picture

This article help me to catalog the media http://www.symantec.com/docs/TECH140538 .

However..this didn't solve my problem, because I still wasn't able to restore individual mail items from AVVI backup. I was only able to see the .vmdk files, but not GRT data. I am pretty sure that backup jobs were successfull, because I am normally re-runnning my monthly jobs if errors occur.

I registered a case with Symantec, and spend hours with support representative to solve this problem. We couldn't find the solution this problem, only thing we were able to do was to duplicate the data to disk storage.

Then we agreed, that I will try to mount the virtual disk with vmware, and use third party tool to mount edb and restore missing mail items to pst file. So, I used Vmware Player to mount the disk, copied the edb from there to usb drive, opened the edb file with VeeAm, and exported missing mail items to PST. Yes, I did it with another backup software..

Actually this looks bad for Backup Exec, because If I face this scenario again (luckily it happens rarely), I have to do this process again, and it takes time.

SOLUTION
CraigV's picture

...if you were trying to restore Exchange data, why did they have you mount the disk with VMware after duplicating to disk? You could simply have duplicated the file to the media server (physical or virtual), and ended up with the *.edb flat-file. Then, using something like Kernel for Exchange, crack open the *.edb and pull out what you needed too.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

villeah's picture

That is what I also would like to find out. After duplicating to disk I was only able to see the virtual disk itself, not what was inside. Like I said, I had to mount it first with vmware.

CraigV's picture

...are you not doing GRT-based backups of that server then?

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...