Slow Mailbox Migration

Hello All
We are in coexistence with 2007 and exchange 2013 and everything is working fine except mailbox migration, which is taking very long.
Mailbox size is average 200MB and migration for 10 mailboxes takes about 12 hours, even within the same LAN and across WAN link
The architecture is
DataCenter 1
2007 Environment
2013 CAS1
2013 Mailbox1
2013 Edge
DataCenter 2
2013 CAS2
2013 Mailbox2
2013 Edge2
Has anyone experienced problems like this before?
Thanks

Hi,
If the servers are performing other higher priority jobs, the mailbox movements will be stalled. When the servers get freed up from higher priority jobs, the mailbox movement resumes.
I recommend you use the New-MoveRequest cmdlet with the Priority parameter to check the result.
If only some mailboxes are affected, you can set the BadItemLimit parameter to a higher value to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Similar Messages

Slow Exchange Migration

I am currently on exchange 2007 SP3 RU11
i want to install exchange 2013, but i'm wondering if I can do the install and slowly test things and migrate
if i run the exchange 2013 install, can i have it coexist on the side but keep everything pointed to my exchange 2007 environment till i'm ready to move over?
currently use
outlook 2013 MAPI clients
outlook 2011 EWS os x clients
active sync clients
no OWA
thanks, couldn't find a lot of info on this.

Yes, you can install exchange 2013 in you current exchange 2007 environment.
When you say slow migration, then I would suggest you the following steps:
1: Cut-Over CAS and MailFlow first to check how things are working, with OWA, AS,Outlook Anywhere etc.
2: Test the Mail flow as it will be flowing via exchange server 2013.
Test all these at least for 1 to 2 weeks
Once you think its working fine, start with Pilot mailbox migration (I choose IT department users)
Test it for a week or so. Test the Public Folder Migration/Replication.
Public Folder replication should be easy and make sure Pilot Users are able to access Public Folder from Exchange 2013 and also they are able to create the Public Folders too.
And once all goes well, you are safe to start full flesh migration.
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
www.exchangeranger.com
Twitter:
LinkedIn:
Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Move Mailboxes from Exchange 2007 to Exchange 2013 (Could not find a valid mailbox migration for esta organization)

Hi all, I am in full migration from Exchange 2007 to Exchange 2013 and everything went correctly.
I have migrated several mailboxes and are working well. But a few days ago, when I try to migrate a mailbox I get the following error and can not migrate:
"Could not find a valid mailbox migration for this organization"
Do you know that you can be?
regards
Microsoft Certified IT Professional Server Administrator

Hi,
From your description, the issue should be related to the migration mailbox. I recommend you check if the following account is existed in ADUC.
Migration.8f3e7716-2011-43e4-96b1-aba62d229136
If this account does not exist, you need to run setup /prepareAD and then enable this migration mailbox to check the result.
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support

Mailboxes migration to new partition

Dear Folks,
We had to migrate the mailboxes from one partition to another, (partition 1 got full). We mounted another disk from SAN (600 GB) the double the size of existing partition (300 GB). How ever after the migration (mailboxes migration from old partition to new) , some how the partition size expanded, old partition was 290 GB and now after migrating the mailboxes to the newly mounted disk, partition size is 380 GB......Here is the question, How we can (OR keep the mailboxes compression) compress the mailboxes to keep the size of partition as it was in old partition (disk) ...???
We are running :
Sun Java(tm) System Messaging Server 6.2-4.03 (built Sep 22 2005)
libimta.so 6.2-4.03 (built 04:37:42, Sep 22 2005)
SunOS msgbak1 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-V490
Many Thanks

Sp00ky_Geek wrote:
We had to migrate the mailboxes from one partition to another, (partition 1 got full). We mounted another disk from SAN (600 GB) the double the size of existing partition (300 GB). How ever after the migration (mailboxes migration from old partition to new) , some how the partition size expanded, old partition was 290 GB and now after migrating the mailboxes to the newly mounted disk, partition size is 380 GB......How did you move the emails from the old->new partition (single user mboxutil -r / copy/rsync the files across?).
Here is the question, How we can (OR keep the mailboxes compression) compress the mailboxes to keep the size of partition as it was in old partition (disk) ...???
If the expansion has occurred due to single-message copy being expanded by the move, you can use the relinker utility to reset the hard-links between identical messages.
The theory behind single-message copy and the relinker utility are described here:
http://docs.sun.com/app/docs/doc/819-2650/6n4u4dttt?a=view#bgaye
Sun Java(tm) System Messaging Server 6.2-4.03 (built Sep 22 2005)
libimta.so 6.2-4.03 (built 04:37:42, Sep 22 2005)
SunOS msgbak1 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-V490I recommend patching to 118207-63 before using the relinker utility to fix bug #6496709 - "relinker should doublecheck"
Regards,
Shane.

Startup slow after migration to new MacBook Pro

startup slow after migration of 2008 MacBook Pro to 2014 MacBook Pro

That crash is citing an issue with a ColorSync profile - the AdobeRGB1998 one.
Try launch ColorSync Utility and see if you can repair it.

Mailbox migration from one server (country 1) to another server (country 2 ) ( exchange 2007)

Hi,
My exchange servers are hosted with my hosting service provider at London, i have 1000 users and each are having 3 Gig mail box size (exchange 2007) and this exchange server is part of our company network which is extended to hosting service provider. I
need to setup new exchange 2007 as part of existing exchange organisation and migrate the users from London to Singapore.
The bandwidth between our company and hosting facility 20 MB.
What is the best method to move the mailboxes from loon service provide to our company ?
I cannot do complete 3 gig mailbox migration from source to destination due to wan bandwidth limitation and time.
I can do only move the mails to local pst then migrate the mailboxes to new server and import the pst mails to exchange mailbox.
Is there any other method available ? backup and restoration ?
Please help me to provide best method for mailbox migration.

For migrating exchange mailboxes from one server to another server (across the country), the suitable approach will be to export mailboxes into pst files.
This job can be simplified even more, take the offline copy of edb file to the destination system (at Singapore) then export all mailboxes (of all sizes) from offline file to separate PST files. Then run PowerShell scripts to import the PSTs. For extracting
mailboxes from offline edb file use a stable edb converter solution that extracts mailboxes (even very large sized) & create new pst file for each of equivalent size.
product overview: http://www.pcvita.com/edb-converter.html

Double Contacts Folder after Mailbox Migration

Here’s a new one for you… I’ve done a few Exchange 2007/2010 to 2013 migrations so far, and to my knowledge they’ve been successful… until now…
I migrated my own server from 2007 to 2013 over the weekend. Mailbox migration finished early Tuesday morning my time (Monday was a public holiday). Everything seemed to work just fine.
Yesterday (Tuesday) I noticed on my Win8.1 phone, that a large number of my contacts were missing. Digging deeper I found that my phone was missing the contacts from my main mailbox. I checked my iPad to see if the contacts were there – they
were! I figured somethings up with my Win8.1 phone, so I removed the account and readded it – same problem. I added a user to the contacts on my Win8.1 phone and sync’d it. It showed up in the iPad no problems.
I then went to Outlook and switched the pane to Folder View – I could then see two contacts folder both at the root of my mailbox. The test user was in the first folder. If I try to expand the 2<sup>nd</sup> folder, it sends outlook
into a massive loop and flickers between the two folders as if they are fighting one on one…
If however I switch the view to People – I see the two contacts folders as just fine and can look into each of them. In one of them I can see the Testuser. In the other folder I can see all my other contacts that are "missing"
But wait… it gets better still. In our office several months back, we migrated from Exchange 2010 to 2013. I wondered if others had seen the problem. From what I can see today, it appears that anyone with a Windows 8 phone has this duplicated
contacts folder. They appear to have the exact same problem… right down to the flickering and crash of Outlook 2013…
I'm concerned now because this is now a couple of migrations that we've seen this on and I've no idea whats gone wrong.
I've checked event logs - nothing seems amiss there.
Any thoughts on how to troubleshoot this?
Wayne
Wayne Small

Hi Wayne,
I have seen this issue if original mailbox was in different language than the new mailbox.I have even seen this even if original mailbox had EN-US and new database is EN-UK.
Please run the following command in Exchange powershell:
Get-MailboxFolderStatistics [email protected] | Select Name,FolderSize,ItemsinFolder
Do you see two contact folder here aswell?
Solution for us it to copy all "old Contacts" to new Contact and delete the old one.When try to delete the default Contact you will get error message that it cant be removed.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Bulk notification before mailbox migration

Hello,
I will start mailbox migration from Exchange 2010 to 2013 per databases. Can you please let me know how I can send out a bulk email notifications to the users in the mailbox database before the migration?
Thanks

$Boxes = Get-Mailbox -Database DB01
Foreach ($Box in $Boxes){Send-MailMessage -Subject "Migration" -Body "your being moved tonight"
-From "[email protected]" -To $Box.PrimarySmtpAddress -SmtpServer "smtp.domain.com"}
That should do it.
DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com

Mailbox migration 2010 SP3 to 2013 error

We have a migration problem, a single 2010 server with all the roles migrating to 2013 with separate CAS and DB roles. Approx 50% of mailboxes are getting stuck and reporting "Transient error MapiExceptionNetworkError has occurred. The system will retry
(1/60)" and "Relinquishing job because the mailbox is locked".
I have tried restarting the services suggested in another thread (Mailbox Migration Service and Search) but it makes no difference.
Any suggestions?
Thanks!
Ben

Hi ,
Please find the below mentioned points.
1.Please share me the output for the below mentioned command.
Get-MoveRequestStatistics -Identity [email protected] -IncludeReport | Export-CSV C:\MRStats.csv
2.Please check the content index state of the target database is healthy and ensure the entire mailbox database status was in healthy state.I mean the database where you are going to move the mailbox.
3.If your exchange 2013 environment is having an single exchange server and target database copy doesn't have the second copy then we need to set the below parameter value to none for that particular database.
DataMoveReplicationConstraint : None
(or)
If your exchange 2013 environment is having an multiple exchange server and target database copy is having the second copy then we can set the below parameter value to secondcopy.
DataMoveReplicationConstraint :Secondcopy
Note : After anyone of the above change ,Microsoft exchange mailbox replication service needs to be restarted.
4.Restart the Microsoft exchange mailbox replication service and check the results.
5. Have you tried moving the same mailboxes to the different databases.
6.Please check the mailbox size which you are trying to move to a different database.Because there might be lot of possibilities to have the target database with limited size.
Please feel free to reply me if you have any queries.
Thanks & Regards S.Nithyanandham

Mailbox Migration Error

I am operating an Exchange 2013 CU7 in a co-exit environment with an Exchange 2010 server. when I try to setup a mailbox migration through the EAC I receive and Error "Multiple potential Migration mailboxes were found for this organization. Please
specify a particular Partition mailbox to use." and I can go any further or finish performing the migration.
any thoughts would be appreciated.

I contacted Microsoft to work through this error message and we were able to get it resolved.
hear is the solution for this error message.
within "Active Directory Users and Computer" in the
Users OU, find and delete the following accounts. (don't worry we will recreate them in a few moments.)
DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}
FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042
Migration.8f3e7716-2011-43e4-96b1-aba62d229136
SystemMailbox{1f05a927-0acd-45d5-9bc1-1a123e6fc52e}
SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}
SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}
Once they are removed, go to your Exchange 2013 server and run the following command from an elevated command prompt
(locate the Exchange Setup File from you CD or download location and run)
Setup.exe /Preparead /IAcceptExchangeServerLicenseTerms (this recreates all the account we just deleted.)
we are almost done. next we have to enable the accounts. This time from 2013 "Exchange Management Shell" run the following commands one at a time.
Enable-Mailbox –Arbitration “DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}”
Enable-Mailbox –Arbitration “FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042”
Enable-Mailbox –Arbitration “Migration.8f3e7716-2011-43e4-96b1-aba62d229136”
Enable-Mailbox –Arbitration “SystemMailbox{1f05a927-0acd-45d5-9bc1-1a123e6fc52e}”
Enable-Mailbox –Arbitration “SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}”
Enable-Mailbox –Arbitration “SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}”
Set-Mailbox "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" -Arbitration –Management:$true
once you have completed this you will be able to close the Exchange Admin Centre, then log back in and go to Migration tab without any errors.

Mailbox Migration Performance Analysis

I'm attempting to follow the steps per this website
http://ppe.blogs.technet.com/b/exchange/archive/2014/03/24/mailbox-migration-performance-analysis.aspx in Exchange PowerShell and Step 4. is returning the following.
ProcessStats : The term 'ProcessStats' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ ProcessStats -stats $stats -name ProcessedStats1
+ ~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (ProcessStats:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
Any suggestions?

No luck with that format for step 1.
PS D:\temp> ..\AnalyzeMoveRequestStats.ps1
..\AnalyzeMoveRequestStats.ps1 : The term '..\AnalyzeMoveRequestStats.ps1' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the
path is correct and try again.
At line:1 char:1
+ ..\AnalyzeMoveRequestStats.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (..\AnalyzeMoveRequestStats.ps1:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
PS D:\temp>

Mailbox migration using JavaMail

Has anyone ever attempted, successfully or otherwise, using the JavaMail API to write a program performing mailbox migration.
Essentially, the task of grabbing all the folders and msgs from one mailbox and putting them into another mailbox.
Thanks!
jrmy

See http://www.jservlet.com/
Use EMail object with Pop3 object (see method EMail.sendRedirect and use IMAP protocol for grabbing all folders)
regards,

Mailbox migration between two Exchange 2013 servers is horribly slow

Hi,
when migrating mailbox between 2 exchange 2013 servers,it s horribly slow. I have found some articles which describing problems about content indexing and missing AD group. This is not my problem, I have tried solutions but it didn't work. Both exchange
are next to each one, same VLAN, same switch. Just migrating between databases.
When I start batch jobs it is migrating only 1 mailbox at once and speed is really slow (2000 - 3000 mail items per 5 minutes). So mailboxes which have 10GB it's migrating 3 hours. My server is on 1gbps LAN.
I have also checked MsExchangeMailboxReplication.exe.config on both servers:
    MaxActiveMovesPerSourceMDB="20"
    MaxActiveMovesPerTargetMDB="20"
    MaxActiveMovesPerSourceServer="100"
    MaxActiveMovesPerTargetServer="100"
    MaxTotalRequestsPerMRS="100"
Do you have any idea where to look why only 1 mailbox is migrating at once?
Thanks

Hello,
For the reason why only 1 mailbox is migrating at once when you start batch jobs, there is no official articles or blog to explain it.
I recommend you check if the speed is slower when you move a smaller mailbox. If the issue doesn't occur, I recommend you set
the AllowLargeItems parameter.
Here are some articles for your reference.
New-MigrationBatch
http://technet.microsoft.com/en-us/library/jj219166(v=exchg.150).aspx
Exchange 2013 Local Mailbox Moves
http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/exchange-2013-local-mailbox-moves-part1.html
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Mailbox migration is very slow

Hi,
Migration of mailbox from Exchange on premises to Exchange online is very slow, 1 GB mailbox took around 5 hours.
Appreciate your quick response regarding same.
Regards,
Hakim. B
Hakim.B Sr.System Administrator

It depends on many factors, there's a long guide here:
http://technet.microsoft.com/library/dn592150(v=exchg.150).aspx
If you have 30 minutes to spend, I also recommend watching the module 3 video from the Office 365 Performance Management course on MVA:
http://www.microsoftvirtualacademy.com/training-courses/office-365-performance-management

Shared Mailbox migrating from Lotus Notes to Exchange

We currently have Lotus Notes and in the process of migrating to Exchange Server 2010. We are using the Quest Notes Migrator for Exchange and the Quest Coexistence Manager for Notes tools.
One of the issues we’re coming across is Shared Mailboxes..
Currently in Notes we have:
Signatures as part of the NSF file so they are included with every email – how will Outlook clients behave for Shared Mailboxes? Because we want the same Signature to be part of every email sent from a shared mailbox regardless of which user sent the email.
We are aware that if we use OWA we won’t have this problem, but how do we configure Signatures for Shared Mailboxes using Outlook clients?
Stationary: We have Stationery linked to our Shared Mailbox accounts, so for example, in our helpdesk mailbox, we have stationary documents/templates we send to end users who email our helpdesk asking a FAQ. Opposed to pointing users to SharePoint, how
do we tackle this in Outlook? Is there options?
Thanks
Ray

Hi,
1. you can use transport rule to have same signature when from field contains shared mailbox email address.
2. Sorry, I don't understand your second question.
Kottees : My Blog : Please mark it as an answer if it really helps you.

Slow Mailbox Migration

Similar Messages

Maybe you are looking for