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
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
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.
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?
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.
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