Link to home
Start Free TrialLog in
Avatar of SM17CH
SM17CH

asked on

NTbackup errors when backing up exchange.

Hey,
Im struggling to find a solution to the error below that come up towards the end of running an exchange backup on sbs2003.

Any ideas

Mitch
----------------------

Backup Status
Operation: Backup
Active backup destination: File
Media name: "exchange 2.1.10 MH.bkf created 03/01/2010 at 12:29 AM"

Volume shadow copy creation: Attempt 1.
Backup of "SERVER\Microsoft Information Store\First Storage Group"
Backup set #1 on media #1
Backup description: "Set created 03/01/2010 at 12:29 AM"
Media name: "exchange 2.1.10 MH.bkf created 03/01/2010 at 12:29 AM"

Backup Type: Normal

Backup started on 03/01/2010 at 12:29 AM.
The 'Microsoft Information Store' returned 'A communications error occurred while attempting to perform a local backup.

' from a call to 'HrESEBackupRead()' additional data '-'The 'Microsoft Information Store' returned 'A communications error occurred while attempting to perform a local backup.

' from a call to 'HrESEBackupRead()' additional data '-'
The operation was ended.
Backup completed on 03/01/2010 at 3:47 AM.
Directories: 0
Files: 2
Bytes: 19,533,214,462
Time:  3 hours,  17 minutes, and  25 seconds

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

The operation did not successfully complete.

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

Open in new window

ASKER CERTIFIED SOLUTION
Avatar of Alan Hardisty
Alan Hardisty
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of SM17CH
SM17CH

ASKER

I assume standard as its just SBS2003 premium.
Can running that scan and fix hurt anything?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Running eseutil /p is not the nicest thing to run against a store and can result in data loss. but we need to rule out database corruption as the cause, so I think you will need to run it if you want to get rid of the errors.
You will need 110% free disk space to run the commands, so please make sure you do.  If you don't, you can either run them with the /t switch followed by "x:\pathtodrivewithmorespace\temp.edb"
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial