cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Jobs fail with db and catalog errors...

jpeterprarch
Level 3

Bizarre.  Backup Jobs are now failing with the catalog and db errors.  What makes this more strange is that there is plenty of free space with the catalogs stored on a disk array with 1.15 TB free.

------------------------------------------------------

The job failed with the following error: An error occurred when writing to the Backup Exec database. A synthetic backup of this resource will not include the data backed up by this operation until the next full or incremental backup of this resource.

------------------------------------------------------

Catalog Error
V-79-10000-10660 - An error was encountered writing to the on-disk catalogs.
A synthetic backup of this resource will not include the data backed up by this operation until the next full or incremental backup of this resource runs.

 

Thoughts?

1 ACCEPTED SOLUTION

Accepted Solutions

Ken_Putnam
Level 6

OK but won't that effectively purge the catalog?

 

Yes it will

You can force BackupExec to re-index it's catalog by following the procedure in 

http://www.symantec.com/business/support/index?page=content&id=TECH35390

View solution in original post

5 REPLIES 5

AmolB
Moderator
Moderator
Employee Accredited Certified

Hello

Rename the existing catalogs folder and create a new catalogs folder at the same

location and then run the backup jobs. Cataolgs folder is located at

X:\Program Files\Symantec\Backup Exec.

jpeterprarch
Level 3

OK but won't that effectively purge the catalog?

Ken_Putnam
Level 6

OK but won't that effectively purge the catalog?

 

Yes it will

You can force BackupExec to re-index it's catalog by following the procedure in 

http://www.symantec.com/business/support/index?page=content&id=TECH35390

jpeterprarch
Level 3

Thanks for the link.  It appears the issue was a recent catalog file that was corrupt.  At first the catalog rebuild did not work until the offending catalog file was removed.  Deleting the *.xml and correpsonding *.fh catalog files from the backup job just prior to the job failures in \Program Files\Symantec\Backup Exec\Catalog took care of the issue.

Ken_Putnam
Level 6

Good

 

If you are satisfied then please close this thread by marking one of the posts as a "solution"