Forum Discussion

Markus_Larsson's avatar
Markus_Larsson
Level 3
19 years ago

Database or database element is corrupt; not a Excange server

Hi!

I have a BackupExec that does a full backup of my FirstClass-server once every week. Each day an incremental backup is done.

Two weeks ago the full backup failed with the error Database or database element is corrupt.
The incremental backup worked perfectly, but the next full backup the same error occurred.

Here is a snip from the log:
Unable to open the item \\MFCIS\F:\FCNS8001\OrgDir\UserIdx\PD2\2 - skipped.
Unable to open the item \\MFCIS\F:\FCNS8001\U\0\1002\MAILBOX\ENINFO - skipped.
WARNING: "\\MFCIS\F:\FCNS8001\U\1\1916\BE8B64DE.DCE" is a corrupt file.
This file cannot verify.
Database or database element is corrupt

And another snip:
Backed up 163915 files in 1972 directories.
1 corrupt file was backed up
28 items were skipped.


Is the error in Backup Exec or in FirstClass?
There have been no problems with any other backup jobs.

FirstClass is a groupware system.

Any help appreciated, Markus
10.x and Earlier
Backup and Recovery
Backup Exec

3 Replies

Sort By
  • Markus_Larsson's avatar
    Markus_Larsson
    Level 3
    19 years ago
    I have been in contact with the support for FirstClass and according to them the file is a corrupt file on the hard-drive.

    So it has nothing to do with Backup Exec.
  • Joshua_Small's avatar
    Joshua_Small
    Level 6
    19 years ago
    I wouldn't be so sure about this.

    Ths is what BE does when a file is in use.

    Consider the AOFO option.
  • Markus_Larsson's avatar
    Markus_Larsson
    Level 3
    19 years ago
    That's true, but.

    The "Network store" (name for the place where all the mail is stored) is mirrored to a second volume.

    The first thing in the backup job is to pause the mirror (the job will not continue if the mirror isn't paused).
    And then the backup is done.
    So the file is not in use when Backup Exec reads it.