What issues are expected when creating a new mailbox for an existing user?

I'm currently in the process of upgrading from Exchange 2007 to 2013, and have been moving mailboxes from the old server to the new one. I have a few mailboxes that are over 20 gigs in size. I've set up limits with the new server to restrict the size to 10 gigs max.

It seems that running archive on some of these mailboxes didn't help much, most likely because the bulk of the e-mail is on the server, but not in Outlook, since it's over a year old. That being said, I figure I have two choice - 1. Delete e-mail older than 1 year on the server to reduce the mailbox size or 2. Create a new mailbox in Exchange 2013, export the data in Outlook to a PST file, disconnect (delete?) the old mailbox, create  a new one on 2013 and import the PST file.

My concern with #1 is that hard drive on the old server is very slow right now, so deleting all that data would take a very long time. I'd like to do #2, but I want to know for sure what issues I would face. I assume internally, the current autocomplete address for this user would not work, but other than that, I don't know how much of an issue this will cause.

Looking for advice on how to proceed. Thanks.
ruhkusAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Seth SimmonsSr. Systems AdministratorCommented:
if you export on the 2007 server, remove the mailbox and create a new one on the 2013 server, with that limit in place the import will fail

better off deleting messages (or move to pst) to get it under the limit then move the mailbox
0
AmitIT ArchitectCommented:
Outlook user will get a bounce back....normally what I do in such case, export everything to PST and then move the empty mailbox to new server and import the data again. If this is not working for you and you want to still create new mailbox, note down legacyexchangedn value for these user, then add X500 custom connector after creating new mailbox with old dn value. This will avoid bounce back for outlook users.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
torns tenkristenIT AdministratorCommented:
Apart from the above suggestions,  I would refer you on this well explained blog that can be a good approach for achieving this task in more appropriate way. It covers all the required aspects for successful migration from exchange 2007 to 2013 : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Moreover, Exchange server deployment assistant is also available from Microsoft that provides step-wise instructions for the same. Please take a look at : http://technet.microsoft.com/en-us/office/dn756393.aspx
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

ruhkusAuthor Commented:
Is the bounceback for Outlook users the only issue when creating a new mailbox?

I've tried the export to PST and deleting from the old server, but all write requests to this server take a ridiculously long time. It would probably be quicker for me to move the 25 gig mailbox intact to the new server, then to try and delete 20 gigs of data off of it first. I've actually contemplated this as well, moving it intact, then running deletes on the new server, but it seems the old server eventually may have issue here as well.
0
AmitIT ArchitectCommented:
You need to troubleshoot slow server issue first. If required increase RAM and CPU. As mailbox move uses lot of resources on a server. Better to do it during weekends.
0
ruhkusAuthor Commented:
The server is 8 years old, one drive in the RAID Is expected to fail soon (likely slowing down the write speeds even more), there's heavy database fragmentation and some other issues. We've already set up a new server, so just have about 10 more mailboxes to move at this point. We'll re-purpose the server for less mission-critical service in the future.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.