Exchange 2007 moving large mailboxes
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.
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.
I'll more recommend to archive the mailbox and reduce the size before moving. Then import the archive back to the mailbox if needed.
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@yourdom
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 DomainControllerNameInTheD
Or if you successfully Installed 2007 you should be able to do a local move request from the EMC,
Then run the following commands
$Localcredentials = get-credential
$Remotecredentials = get-credential
PrepareMoveRequest.ps1 -Identity firstname.lastname@yourdom
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 DomainControllerNameInTheD
Or if you successfully Installed 2007 you should be able to do a local move request from the EMC,
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.c
$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\Storage
$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=doma
$mailbox = get-mailbox $MB -DomainController $SDC
Move-mailbox $mailbox.Identity -TargetDatabase $tdb -GlobalCatalog $GC -SourceForestGlobalCatalog
If in same org and same forest, do the following:
#Replace $variables with your settings
$MB = "MAILBOXNAME"
$SDC = "SOURCE DOMAIN CONTROLLER FQDN"
$tdb = "DESTINATIONSERVER\Storage
$mailbox = get-mailbox $MB -DomainController $DC
$GC = "Domaincontroller.domain.c
$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.
#(replace $tdb and $gc and mb with your settings)
$tdb = "Server/storagegroup"
$gc = "Domaincontroller.domain.c
$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\Storage
$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=doma
$mailbox = get-mailbox $MB -DomainController $SDC
Move-mailbox $mailbox.Identity -TargetDatabase $tdb -GlobalCatalog $GC -SourceForestGlobalCatalog
If in same org and same forest, do the following:
#Replace $variables with your settings
$MB = "MAILBOXNAME"
$SDC = "SOURCE DOMAIN CONTROLLER FQDN"
$tdb = "DESTINATIONSERVER\Storage
$mailbox = get-mailbox $MB -DomainController $DC
$GC = "Domaincontroller.domain.c
$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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.