Backup Exec/Exchange - cannot backup the information tore/First storage group....

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Evening guys

I've got issue with Symantic Backup exec 12.5 on server 2003

The following error appears in the job log, the job is failing.

'MICROSOFT INFORMATION STORE\FIRST STORAGE GROUP\MAILBOX STORE\ IS A CORRUPT FILE

THIS FILE CANNOT VERIFY

Event logs - Source: MSEXCHANGE IS MAILBOX
ERROR ID 1022
LOGIN FAILURE ON DATABASE FIRST STORAGE GROUP\MAILBOX STORE'

Now, the users have no issues with their email so it's only within Backup Exec where the issue is being raised. I have looked at permissions and the service account used to run this job has full access to the database to back it up, but the backup still fails. I've changed the exchange maintenance schedule not to run at the same time as the backup.

Looks like the store is working as it should, just that BE seems to report it's corrupt

Any ideas how I can get the mailbox store to successfully back up?

Cheers

 

Hi Sparky - cheers for the reply. I've been checking permissions on the service account that is used by BE by manually going through Exchange manager trees and the relevant folders in explorer. I haven’t used the test function in BE before, but it sounds just what I needed (would of saved a heap of time). If this checks out, I was thinking the next step would be to check the database integrity using ISINTEG AND ESUTIL, etc. You're statement about users being able to access email but the database being corrupt has prompted this - damn! What do you think? Any other steps I could take before using these tools on the dismounted store?

 

Good man, I'll check the logs tomorrow and post them up.

I've made sure the service account has top level access in ESM and drilled down to every folder. I'll run the backup test as well.

The backup was running sweetly for years but then all of a sudden it failed with the error stated. Do you think this is a permissions issue rather than the actual database requiring a defrag or similar?

 

Yeah, I'm a little apprehensive running defrag tools on a database until I know for a fact it's corrupt. If i do run these tools would a NT backup of both the private and public database be adequate to restore from in case of any issues? I was also thinking about PSTing off the users email before commencing any of these utilities.

Nice one Sparky, I'll run a test backup tomorrow and check permissions through BE. I'll grab the logs and get post them up tomorrow night. Cheers once again lad.

 

Sparky - I ran the integrity check and it came back with corruptions. I then ran the ESEUTIL repair command and it sorted the issue Cheers once again for your help mate.

 

Basically Exchange server error 1022 occurs at the application level. When an Exchange server denies the accessibility of the database page from the Operating System, then in this situation of not getting the page in return causes error id 1022. The main cause of the error is a database file corruption issue.