Avatar of magapie
magapie
Flag for United States of America asked on

2010 mailbox move

I have a 2003 and 2010 server. Performing a mailbox move is quite a time consuming experience. I first thought that the mailbox was too big. So I picked a smaller one of 1.75 gb. It gets to 25% and stops. There's a gig switch between the servers. I'm not sure why it takes so long and/or fails.
Exchange

Avatar of undefined
Last Comment
flaphead_com

8/22/2022 - Mon
flaphead_com

where are actually performing the mailbox move?  you should use Exchange 2010 to do the actual move, by creating a move request.

You need to pull to Exchange 2010 and not push from Exchange 2003

I have done quite a lot of 2003 to 2010 move and they fly
ASKER CERTIFIED SOLUTION
alwayzexchange

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
magapie

ASKER
I'm in 2010 pulling the old mailbox over. Right now it's been 8 hours and only 61% complete on a 1.76gb mailbox.
peterdilorenzo

Magapie - are you using local disk storage on both Servers?  If so, this is def your problem.  The GB link speed is not going to matter, it is all about disk i/o.  If you are using SAN's you would be getting those 2GB mailboxes finished in under 20 minutes.  Of course, this point assume you are using local storage.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
magapie

ASKER
Well this is a small office and there is no san. These servers are not under any i/o stress.
peterdilorenzo

It is not the "stress" factor, it is literally the speed of the SAS drives and/or configuration.  Such as what RAID, what kind of drivers, speed of drives etc.

I would run Perfmon while you're moving a mailbox and look at your disk I/O counters.  I bet you that will tell you more than anything.
magapie

ASKER
I skipped using 999 and it still stalls out. It's not a san issue. I deal with disk i/o all day long. If it was the disk it would just be slow. This is stalling out at 25%. Is there a verbose logging or error log?
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
peterdilorenzo

magapie

ASKER
Those are good articles. The performance issue has more to do with moving multiple mailboxes. I'm just trying to move one at a time. it stops on 25% then takes hours to finish.
magapie

ASKER
[PS] C:\Windows\system32>Get-MoveRequest | ?{$_.status -eq "InProgress"}| Get-MoveRequestStatistics | ft Disp*,Per*,Byte
sTransferredPerMinute

DisplayName                                                     PercentComplete BytesTransferredPerMinute
-----------                                                     --------------- -------------------------
Eric Middleton                                                               10 67.86 KB (69,492 bytes)

As you can see it is crawling.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
flaphead_com

Damm that is really slow, assume the nework between 2003 and 2010 is good?

On a LAN i have been getting upto 100MB/sec
flaphead_com

did the move complete? How long did it take?
flaphead_com

was any of the information useful? do you want to award points and close?
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.