by "kcirredd"<der@[EMAIL PROTECTED]
>
Aug 10, 2007 at 05:27 AM
I encountered this problem with backup exec10d, after a lot of
troubleshooting we realized that ex10d recognixed a file as corrupt if it
has been modifide before verification is completed, eg. our backup rins
overnight but the verification process is not completed before users
starts
using exchange in the morning of the following day, when the backup
program
reaches the information store to verify, it cannot as it result it re****ts
the exchange information store as "corrupt" there is an option to ignore
but
a will have to search and get back to you on it.