GSI Guy
asked on
Mailbox Exports keep failing
OK, the subject pretty much says it
Despite running repairs on said mailboxes, several of the mailboxes on our Exchange server keep failing when being exported.
The error message is Too many bad items.
The command I am trying to use to repair the boxes is:
Anybody got any helpful ideas?
Thanks in advance!
Despite running repairs on said mailboxes, several of the mailboxes on our Exchange server keep failing when being exported.
The error message is Too many bad items.
The command I am trying to use to repair the boxes is:
New-MailboxRepairRequest -Mailbox <<MailboxName>> -CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,Folderview}
Anybody got any helpful ideas?
Thanks in advance!
ASKER
EMS.
It's a nightly batch script.
It's a nightly batch script.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK. ESEUTIL would require us to take the entire database offline, and then reseed it from the repaired server (It's in a DAG), IIRC.
Would exporting using Outlook allow us to detect and or remove the corrupted item?
Would exporting using Outlook allow us to detect and or remove the corrupted item?
Ok I see it is always complex to repair database.
Outlook is able to export in PST even there are some objects are not repaired. Sometimes the corruption is only deleted items, categories,.. very small but with the mailbox repair is not able to fix it.
Outlook is able to export in PST even there are some objects are not repaired. Sometimes the corruption is only deleted items, categories,.. very small but with the mailbox repair is not able to fix it.
ASKER
Hmmmmm.
I'm trying to do this while minimizing the downtime for users.
I would think that your Outlook option would be the first option to try. I will see if that works.
Failing that, I suppose I could move all functional users over to a new database and replicate, and then run ESEUTIL on the problem ones in the old database.
I'm trying to do this while minimizing the downtime for users.
I would think that your Outlook option would be the first option to try. I will see if that works.
Failing that, I suppose I could move all functional users over to a new database and replicate, and then run ESEUTIL on the problem ones in the old database.
HI,
If there is problem in exporting the Exchange Mailbox then you prefer this article to resolve your problem
Exchange Mailbox Error
Hope this will help you
Christ
If there is problem in exporting the Exchange Mailbox then you prefer this article to resolve your problem
Exchange Mailbox Error
Hope this will help you
Christ
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As Ajit mentioned, you need to use the -badlimit switch...turn it up to at least 10000, also use the -AcceptLargeDataLoss switch, set that at a decent number as well if you are exporting mutiple mailboxes.
ref link: https://technet.microsoft.com/en-us/library/ff607299(v=exchg.160).aspx
ref link: https://technet.microsoft.com/en-us/library/ff607299(v=exchg.160).aspx
You can get the help of Eseutil function to restore Exchange databases. If you want to know about the Eseutil function, then visit here: https://technet.microsoft.com/en-us/library/aa998075(v=exchg.65).aspx
ASKER
ESEutil combined with the baditemlimit switch fixed our problem. Thanks!
Are you trying to export from ECP or EMS?