Why Maibox Export Request to copy mailbox contents to PST work quite badly?

This is using MS Exchange Server 2010 with SP1. There are 2 CAS, and 3 Hub Transports + Mailbox servers. The objective is we wanted to backing up 30+ mailboxes into PST files, and then remove those mailboxes. We are using MS Exchange Mailbox export request utility. We also granted the "exchange trusted subsystem" the read/write permissions on the nas storage.

At first , we granted few of our accounts "mailbox Import Exports" role. After that, for each mailbox that we want to export as PST, we type:

    - new-mailboxexportrequest -mailbox mailboxxxx -filepath "\\nas1\exchange mailbox archives\mailboxxxx.pst"

Type "get-mailboxexportrequest" to make sure that the above request is in queue.

Type "get-mailboxexportrequeststatistic -identity "mailboxxxx\mailboxexportx", to see the progress in percentage

After, proceed with the second and subsequent mailbox export.

we type in get about 10+ mailboxes in queue. However, the progress seems very slow, with only 2 GB of the mailbox contents completed in 12 hours. After waiting for about 4 days, I typed "get-mailboxexportrequest" again, and to my surprise, found about 6 mailboxes were completed but failed.

Why these mailboxes failed to export, and some more they were exported in the slow pace? Anywhere to increase the speed?
LVL 1
MichaelBalackAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Marshal HubsConnect With a Mentor Email ConsultantCommented:
Please refer this article. Hope it will work in you case!!
0
 
Niten KumarPrincipal Systems AdministratorCommented:
Try exporting one mailbox to a different storage, possibly a network share drive on another server to see if gives any difference in performance.  Just to eliminate the NAS storage as the problem.  For the failed mailboxes can you post the error. Thanks
0
 
Simon Butler (Sembee)ConsultantCommented:
2010 SP1? Really?
I would upgrade before you do anything else - there were significant changes to the export method in SP2 I believe, but skip that and go to SP3 and then the latest rollup. No one should be on a five year old version of Exchange 2010.
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
MichaelBalackAuthor Commented:
Hi Simon,

We also think of upgrading to sp3, but still waiting for the downtime to be granted. In long term, we go for sp3, but now, we can't, and we still have to stick to sp1.
0
 
MichaelBalackAuthor Commented:
Hi NitenKumar,

Felt that NAS may not be the root cause.
0
 
MichaelBalackAuthor Commented:
Hi Marshel,

I have started the second round. This time round, only 2 or 3 mailboxes on the queue. I also put in the 2 parameters - baditemlimit, and acceptlargedataloss. I will monitor for the changes
0
 
Niten KumarPrincipal Systems AdministratorCommented:
Noted.  Just as a precaution you also might want to check the event viewer (Application logs) on the mailbox server where the database is hosted.  If you are getting bad item during export then it can possibly be database corruption.  Thanks.
0
 
MichaelBalackAuthor Commented:
Hi all,

After adding in the parameters -baditemlimit, and also -acceptlargedataloss, no more mailbox export fail. However, exporting process still quite slow.

As for the destination to store those pst files, I also moved it to the local exchange server, but doing so didn't improve the process.
0
 
MichaelBalackAuthor Commented:
Thanks for Expert - Marshal in suggesting with 2 parameters, and none of the mailbox ended with fail.
2
All Courses

From novice to tech pro — start learning today.