Solved

Exchange 2007 moving large mailboxes

Posted on 2010-09-01
4
463 Views
Last Modified: 2012-05-10
Anyone have any experience (good/bad) with moving large mailboxes from Exchange 2003 to Exchange 2007? By large I mean 30 GB each, with about 80,000 items.

Was it successful? Did you use the wizard or cmdlet? Are there any MS documentation or recommendations for this? I'm concerned about data loss or corruption because of the size. I can estimate how long it will take. Thanks.
0
Comment
Question by:donken99
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
4 Comments
 
LVL 9

Expert Comment

by:pcchiu
ID: 33579754
I'll more recommend to archive the mailbox and reduce the size before moving.   Then import the archive back to the mailbox if needed.

0
 
LVL 11

Expert Comment

by:JuusoConnecta
ID: 33585873
Have moved 10 gb mailboxes from ex 2003 to ex 2010. Did this with powershell and worked fine. If the move is towards another domain I would suggest using the Script from microsoft called "PrepareMoveRequest.ps1"

Then run the following commands

$Localcredentials = get-credential
$Remotecredentials = get-credential

PrepareMoveRequest.ps1 -Identity firstname.lastname@yourdomain.com -RemoteForestDomainController DomainControllerNameInYourRemoteForest -RemoteForestCredential $RemoteCredentials -LocalForestDomainController DomainControllerNameInYourCurrentForest -LocalForestCredential $LocalCredentials -TargetMailUserOU "OU=Stockholm,OU=YourOU,DC=yourdomain,DC=com"

And then (either if the move is to another exchange organization or the same organization run the following):

New-MoveRequest -Identity UPN or Username -RemoteLegacy -TargetDatabase "Mailbox Database 1891317102" -RemoteGlobalCatalog DomainControllerNameInTheDomain -RemoteCredential $RemoteCredentials -TargetDeliveryDomain YourDomain.com

Or if you successfully Installed 2007 you should be able to do a local move request from the EMC,
0
 
LVL 12

Expert Comment

by:GusGallows
ID: 33627638
Are the Exchange 2003 and Exchange 2007 servers in the same forest/domain? If so, the move-mailbox cmdlet works great. I have had no issues moving mailboxes even upward of 15gb. They may take a while, but 2007 is excellent at preventing data loss during a move. If something happens to terminate the cmdlet prematurely, it will revert to 2003 with no loss. The only issue I have seen is when I try to send it again, it will say the mailbox already exists, but then will clear the 2007 "ghost" and allow it to move on the next attempt. The command would be something like this:
#(replace $tdb and $gc and mb with your settings)
$tdb = "Server/storagegroup"
$gc = "Domaincontroller.domain.com"
$mb = "MAILBOXNAME"
move-mailbox -identity $mb -TargetDatabase $tdb -BadItemLimit '10' -GlobalCatalog $gc -confirm:$false
 
If you are moving same forest but between different domains the cmdlet still works but is a bit more complex.

If in different org but same forest, do the following:
$MB = "MAILBOXNAME"
$SDC = "SOURCE DOMAIN CONTROLLER FQDN"
$tdb = "DESTINATIONSERVER\StorageGroup\DATABASEName"
$GC = "DestinationGC.domain.com"
$SGC = "SOURCEGC.domain.com"
$OU = "OU WHERE YOU WISH TO PLACE THE AD ACCOUNT IN THE DESTINATION DOMAIN"
#I.E "Ou=NUser,ou=Users,dc=domain,dc=com"
$mailbox = get-mailbox $MB -DomainController $SDC
Move-mailbox $mailbox.Identity -TargetDatabase $tdb -GlobalCatalog $GC -SourceForestGlobalCatalog $SGC -NTAccountOU $OU

If in same org and same forest, do the following:
#Replace $variables with your settings
$MB = "MAILBOXNAME"
$SDC = "SOURCE DOMAIN CONTROLLER FQDN"
$tdb = "DESTINATIONSERVER\StorageGroup\DATABASEName"
$mailbox = get-mailbox $MB -DomainController $DC
$GC = "Domaincontroller.domain.com"
$OU = "OU WHERE YOU WISH TO PLACE THE AD ACCOUNT IN THE DESTINATION DOMAIN"
Move-mailbox $mailbox.Identity -TargetDatabase $tdb -GlobalCatalog $GC -NTAccountOU "$OU

If it is outside of the forest, I am not sure of how to pull that with anything other than a migration tool such as Binary Tree or QWEST migration tools.

0
 

Accepted Solution

by:
donken99 earned 0 total points
ID: 33743688
Thanks for comments. We do have Enterprise Vault but there are delays getting it installed. So I used the wizard and successfully moved a test mailbox of 35.5 GB/250,000 items in 10 hours.
0

Featured Post

PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to install and use the NTBackup utility that comes with Windows Server.
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

724 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question