Hi.

Although ive found many answers on here, ive never asked or contributed to the forum, so thank you for asking and answering everything i have already had to find! :)

This time however, i cant find any answers... I am running a new-mailboxexportrequest on a series of mailboxes in an exchange 2013 dag environment and they are failing, each at a different point in 'size' and there is no correlation to when, or why the mailboxexportrequests fail. However, if i move individual mailboxes to a different mailstore on the same server, i can instantly export the items within the criteria i need to. I have repaired both the mailbox and the database before i have resorted to moving and both repair jobs finish successfully.

Any ideas welcome, i have tried everything i can find on the internet already, but the exportrequests will not move past a certain point in time before i move the mailbox to another store first

Cheers all! :)

1. Hmm very odd, corruption would have been my first thought
2. for the new DB your transferring users to is that DB on the same server as the problem DB or a different server?
3. IF both DB's are on the same server then same question regarding Disk i.e. is that NEW DB on the same disk as the problem DB or a different disk?

As you have already tried repairing both mailboxes before restoring them.

I would suggest you to give a try on any commercial application like, (http://restoreexchange.net/) that might be a good alternative approach in order to repair corrupt mailboxes, restore them back into previous used format and migrate to new server accordingly.

Hello 

Pls check if you are member of a discovery management role and the problematic database is also in the management scope. Database from where you are able to export may already be in scope.

Hi goodevans,

Thank you for your question.

We suggest you post move command and entire error for our troubleshooting.

As Troy said, we could change the value of corruption to check if the issue persist. We could refer to the following link to move mailbox:

https://technet.microsoft.com/en-us/library/dd351123%28v=exchg.150%29.aspx

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Thanks, however once i have moved the mailbox, I use the same account and achieve 100% success... I will have a look at the Database to ensure it is in the management scope though!

Hi Jim, 

Thanks for your answer, I have contemplated batch moving the mailboxes to a new database before exporting them, (which would also be a good excuse to clean the databases) however, I don't see why i should have to, i have checked the Database & mailbox for corruption and it has come back clean, I'm just intrigued i guess. One thing that I should probably have mentioned is that i have migrated the mails into EX2013 from EX2003 using Dell Quest Migration Manager.... not sure if that has any bearing on Exchange seeing the mail as corrupt if it is not?

Sure - here is the command, ill return an error when it runs

$Databases = Get-MailboxDatabase | Where-Object {$_.Name -like "LDN*"}
ForEach ($Database in $databases)
    {
    $ExportUsers = Get-MailboxDatabase $database | Get-Mailbox

        ForEach ($ExportUser in $ExportUsers)
         {
        $alias = $exportusers.Alias
        $filename = "$alias@lsh.co.uk.pst"
        New-MailboxExportRequest -Mailbox $ExportUser -FilePath "\\Filepath\ExchangeData\LondonShortfall\$database\$filename" -ContentFilter {(Received -lt '04/01/2015') -and (Received -gt '06/01/2012') -or (Sent -lt '04/01/2015') -and (Sent -gt '06/01/2012')}
         }
    }

• Edited by goodevans46 19 hours 20 minutes ago

Hi Troy, 

Thanks for your reply, i am looking at corruption too but i have attempted to repair the mailbox, and the database? would this not also look for corruption?

The new DB is on the same server, and the same partition as the original. Its worth mentioning i have recently completed a migration to EX2013 from EX2003, using Dell Quest Migration Manager.

Regards

Hi Jim, 

Thanks for your answer, I have contemplated batch moving the mailboxes to a new database before exporting them, (which would also be a good excuse to clean the databases) however, I don't see why i should have to, i have checked the Database & mailbox for corruption and it has come back clean, I'm just intrigued i guess. One thing that I should probably have mentioned is that i have migrated the mails into EX2013 from EX2003 using Dell Quest Migration Manager.... not sure if that has any bearing on Exchange seeing the mail as corrupt if it is not?

Sure - here is the command, ill return an error when it runs

$Databases = Get-MailboxDatabase | Where-Object {$_.Name -like "LDN*"}
ForEach ($Database in $databases)
    {
    $ExportUsers = Get-MailboxDatabase $database | Get-Mailbox

        ForEach ($ExportUser in $ExportUsers)
         {
        $alias = $exportusers.Alias
        $filename = "$alias@lsh.co.uk.pst"
        New-MailboxExportRequest -Mailbox $ExportUser -FilePath "\\Filepath\ExchangeData\LondonShortfall\$database\$filename" -ContentFilter {(Received -lt '04/01/2015') -and (Received -gt '06/01/2012') -or (Sent -lt '04/01/2015') -and (Sent -gt '06/01/2012')}
         }
    }

• Edited by goodevans46 Thursday, July 30, 2015 12:08 PM

ok so two things

1.  Yes I would highly recommend that you  repair mailbox and then a DB but only after a complete backup just in case something goes south.

2. Ok so in terms of products the Dell/Quest products is one of the top 3 products on the market and Lucid8 is one of them.  That said this is something we discovered with Quest in 2010.  Great product overall but makes me personally wonder how much valued testing is being done.....  

3. if you want to test, A: make a new DB, B: make a test user, C:migrate older user to test user, D: test export

Hi goodevans,

By my understanding, we must assign permission before we want to run New-MailboxExportRequest. We could refer to the following link:

https://technet.microsoft.com/en-us/library/ff607299(v=exchg.150).aspx

In addition, please post entire error information or snapshot to us for troubleshooting.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Hi Troy,

Im looking at utilising DigiScope as a third party tool to perform the export, since i had a support session with Microsoft and it turned out i have to move all mailboxes before i can export them, i simply dont want to waste the time or space on data that will be archived after the export has completed. Could you tell me if DigiScope will allow me to export all mail items into individual pst files based on date criteria in the same way a new-mailboxexport would?

Thanks

Good morning, yes you can export all data into individual PST files bases on date criteria as well as other parameters and you can see it visually once a filter is applied which can be simple, i.e. date range items were created, modified or more complex, i.e. only items with words, phrases, values etc. For example in image below the DEMO DB of Andy Jacobs Mailbox you can see that

* There are 42 items (look at mailbox folder and item count to the right)

* on the right you will notice its only showing 24 items and that's because I created a FILTER to ONLY show items that were created between 1.1.2008 and 12.31.2008 and I named that filter "Created in 2008" which you can see in the upper right hand quadrant.

* you will also notice that the background is a yellow/off white which is a visual indicator that a filter has been applied

* Once a filter is applied you can then export specific mailboxes, folders or the entire DB and the filter will be applied.

* The default is to create a PST per mailbox