I have around 1000 mailboxes on a single Exchange 2007 mailbox server.  I am moving batches of about 30 mailboxes a day and it's taking a full 24 hours to complete. The target Exchange Environment is Exchange 2013 with 4 servers (2 CAS and 2 DAG) members for redundancy in the same site at as the 2007 servers. Everything is connected by 10GB infrastructure. h servers have 16GB of ram and back onto an EMC array of disks. I have not run through the exchange sizing calculator yet. But did run the jet stress tool before moving client mailboxes over.

During the moves some of the mailboxes are dropping into a stalled state, but will resume and complete. The concern I have however is that there is only about 1GB of mail being moved an hour. I expect that exchange 2013 may be throttling the move somewhat but do see 10 - 15 mailboxes in the batch reporting copying messages.

Questions

1, Can I increase the performance of the moves by changing throttling settings for the mailbox moves?

2, I am currently running a EXBPA performance 2 hour performance check on the Exchange 2007 server, would there be something equivalent to run on the 2013 servers without diving into perfmon counters?

Just wanting to identify the cause of the slow performance.

Thanks

  

Hello

tip:
disable virusscan if have.
if create new db on exch 2013 need restart information store if missing its can be slow.
because you have got more database, you can create more movereq to different database that are on different mailbox node mounted.
disable indexing whil move mailbox Set-MailboxDatabase DB -IndexEnabled:$False

Hi BTRowdy,

Base on my search, I recommend you try using the following methods and check if any helps to increase the performance:

1. Run the following commands on your exchange 2007 server and then reboot the server:

netsh int tcp set global chimney=disabled
netsh int tcp set global rss=disabled

2. Check if there is a security group that is named "ContentSubmitters" in your exchange 2013,

if no, you need to create this group manually through the following steps:

• Create a new Active Directory group that is named "ContentSubmitters" and then grant Admistrators and NetworkService full access to the group. This is a dummy group and should be used as a placeholder only. You might want to add a description so that the group is not removed.
• Force or wait for Active Directory replication.
• Restart the following services:
  • Microsoft Exchange Search
  • Microsoft Exchange Search Host Controller

Best regards,

I do receive a message about a database missing in the event log. I think restarting the Information Store service is a good idea. Thanks

I will try that indexing option and the realtime exchange aware anti-virus.

I have a change control in to set these Network Settings on the Exchange 2007 server and will reboot and report back.

The group "ContentSubmitters" does not exist. I will try creating this as you mention above.

Thanks

I changed the TCP options on the Exchange 2007 server and rebooted. I have disabled anti-virus, indexing and have restarted the Information Store on the 2013 servers. I queued up 150 moves in 2 batches coming from 2 different databases. I now see that 60% are in the ReliquishedwlmStall, 35% Reliquished, 2% copying messages, 3% completed. 

Any suggestions?

Hello

please copy one mailbox move error log which is  ReliquishedwlmStall:
get-moverequest -ide mailbox | get-moverequeststatistics -includereport  | fl

Whats happening with I/O, Network throughput and CPU on the respective servers during the moves?

Yes, you can increase your speed of migration, I would refer you to try these following methods and check if these helps:

1. Check out if there is any content index error on your mailbox database copies, If it is there, try to disable the index and check you can see the difference.

Get-MailboxDatabaseCopyStatus  | ft name, status, contentindexstate,contentindexerrormessage

Set-MailboxDatabase DB -IndexEnabled:$False

2. Check out your NIC card drivers that if they holds latest drivers. Perfrom a test on copying 100 MB file from the source server to the target server. Try to the check its speed.  Verify with the hardware vendor if there are any latest drivers released for the server hardware.

3. Disable the TCP Chimney

Check the TCP Chimney is Enabled and supported

Netsh int tcp show global

Netsh int tcp show chimneystats (Check the Supp value, if its No that means TCP Chimney is not supported or not enabled on the Network card driver settings, otherwise youd see Yes with some values on TMax and PMax)

To disable TCP Chimney and RSS:

netsh int tcp set global chimney=disabled
netsh int tcp set global rss=disabled

By following these methods above you can identify the cause of the slow performance and can fix those in a manual way. But as you have 1000 mailboxes to migrate, it would take time to migrate all these mailboxes manually. To save your time and efforts, I would recommend you to use any automated software like Stellar Mailbox Extractor for Exchange Server,  which can provide you hassle-free environment to get this job done quickly.