Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1586
  • Last Modified:

Exchange 2007 Restore from NT Backup

I am using NTBackup to backup and restore exchange 2007 in my lab however I am having issues doing a restore...using the toolbox, its showing a clean shutdown status...but when I do the restore from the RSG its showing corrupted items and unable to move...

Error restoring the mailbox (/O=ORG/OU=EXCHANGE ADMINISTRATIVE GROUP (123)/CN=RECIPIENTS/CN=JohnDoe). Error message is: Error was found for John Doe (JohnDoe@test.local) 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.

Mailbox (John Doe) has been restored successfully. Status Code: -1056749110. Status Message: Error occurred in the step: Moving messages. This mailbox exceeded the maximum number of corrupted items specified for this move mailbox operation.
0
kf4ape
Asked:
kf4ape
  • 5
  • 4
1 Solution
 
Exchange_GeekCommented:
Seems, more of corruption in the mailbox - you may want to export-mailbox to some other existing mailbox. Try opening the mailbox in OL and check out for those corruption.

Btw is this taking place with every user / specific one ??

0
 
kf4apeAuthor Commented:
every user...tempted to run eseutil on the db
0
 
Exchange_GeekCommented:
I am still amazed how did this database got backed up in its first place. If DB was in a corrupted state, it is normal that a normal check sum test would fail and backup would fail inevitably.

Instead of running eseutil - why not work with isinteg and get through the -fix test.

Eseutil could be used as a last option not first.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
kf4apeAuthor Commented:
no joy still...did a full backup via ntbackup, mounted an RSG, mounted DB, allowed overwrite, and still issues...

the ISINTEG found a few issues and corrected them
0
 
Exchange_GeekCommented:
Seems, either corruption level is way too high or Exchange is behaving dumb.

Let me check something quickly - if you're in a hurry you may run a hard repair - il post my finding in some time.

0
 
kf4apeAuthor Commented:
thanks!!!
0
 
Exchange_GeekCommented:
I consulted few of my MSFT colleagues - they too are amazed at this issue when i discussed with them, they also suggested working with repair - however, suggested to take another backup once the repair is over and merge is done.
0
 
kf4apeAuthor Commented:
Thank for the info...the database is only like 1.4gb so relitivly small (so to speak)...I will do this test tonight when I get home...

thanks again
0
 
kf4apeAuthor Commented:
Repair didnt work either, isinteg -test alltests didnt showanything either...so I decided to create a new database and moved a few users over...did not recieve any errors on relocation...I was able to backup and recover it perfectly...just going to perfrom some more test restores...I am wondering what the heck happened...wonder if was the backup util I was testing, Iron Mountain's live vault, couldnt do a successful restore so I went back to flat file
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now