Link to home
Start Free TrialLog in
Avatar of GDB Ian
GDB IanFlag for United States of America

asked on

Exchange 2007 Recovery Storage Group Mailbox Merge Issue

I am running Exchange 2007 with SP1 on a Windows 2008 server with the Hub Transport, Mailbox and Client Access roles on the single server.  We back up the Exchange 2007 server nightly with Backup Exec 11D.  Today I created a recovery storage group for one of our mailbox databases.  I then restored the mailbox database from a backup tape to the recovery storage group successfully.  I have run into problems however when trying to restore(merge) a mailbox from the recovery storage group into the production storage group.  The error I am receiving is "Error restoring the mailbox (/O=GUIDE DOGS FOR THE BLIND/OU=GDB/CN=RECIPIENTS/CN=SSMITH). Error message is: Error was found for Steve Smith (ssmith@guidedogs.com) because: Error occurred in the step: Moving messages. This mailbox exceeded the maximum number of corrupted items specified for this move mailbox operation., error code: -1056749110.  This happens for any mailbox I attempt to merge. Has anyone ever seen this and know of a fix?
ASKER CERTIFIED SOLUTION
Avatar of Chris Dent
Chris Dent
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 GDB Ian

ASKER

I've changed the bad item limit to 1000 and tried. Unfortunately it appears that Exchange 2007 thinks all of the items are corrupt. The jobcompletes when the bad item limit is set higher than the number of messages in the mailbox.  Unfortunately, no items are then merged as all are seen as corrupt I guess.
I have worked on the same issue. In my case we ran an ISINTEG on the database that is in the RSG
http://support.microsoft.com/kb/182081 
The command to run is:
 isinteg -s <servername> -fix -test alltests
 
After this completes run the merge again
Avatar of GDB Ian

ASKER

Isinteg found a couple fixes, but still no change.  
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