Corrupted Catalog File in Backup Exec

Learn how to repair a corrupted catalog file that can occur when using Backup Exec 8.5 and Backup Exec 8.0.

Bob Chronister

March 18, 2001

1 Min Read
ITPro Today logo in a gray background | ITPro Today

I recently upgraded from VERITAS Backup Exec 8.0 to Backup Exec 8.5. I've purchased Microsoft Exchange Server support and am using Backup Exec to perform a brick-level (i.e., message-by-message) backup of the Exchange Server mailboxes. The process works, but I'm now seeing individual email items appear in the Information Store (IS) as a group of mailboxes. Also, Backup Exec doesn't display email subject lines. Recently, the server in question ran out of disk space, but I don't think that problem is related to my current problem. Do you know what's going on?

Your problem seems to be specific to Backup Exec 8.5 and Backup Exec 8.0, and the culprit is a corrupted catalog file. Fortunately, this problem is fairly easy to repair.

Go to your Backup Exec application directory, and find the catalog directory. Rename this directory catalogold (or something similar) to show that this directory isn't the current catalog directory. The next time you run Backup Exec, the application will recreate the catalog directory and start a new catalog file.

You might want to scan through old catalog files to try and determine when the catalog problems began. If you can find the instance, then you should be able to copy all catalog files dated before the apparent corruption to your new catalog directory. After you do so, prior backed-up catalog files will be visible in Backup Exec, and restoration from earlier backups will be easier.

Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.

You May Also Like