Finally, mount the database:
Mount-Database -Identity ???ca100\SG1Temp\Mailbox Database???
6. Before clients can access the database, they must be re - homed to the SCR target. The following
example moves all of the mailboxes from the SCR source to the SCR target. Note the example
prevents system accounts from being included.
Get-MailboxStatistics -Database mb100ccr\first storage group\mailbox database
|where {$_.ObjectClass -NotMatch ??? (SystemAttendantMailbox | ExOleDbSystemMailbox)??™}
| Move-Mailbox -ConfigurationOnly -TargetDatabase
???ca100\Sg1Temp\Mailbox Database???
For scenarios with the SCR source as an SCC or CCR cluster, a few additional steps need to be run in
order to prevent any conflicts when the failed source is brought online.
In this example the CCR cluster, mb100ccr, is made of an active node (mb100) and the passive node
(mb101). Bring up mb100 first, then mb101. The Clustered Mailbox Server will remain offline to prevent
duplicate names on the network.
1. On the node that owns the resource group for the Clustered Mailbox Server, run setup to clear
the CMS and its resources. The following command is run on mb100:
Setup.com /ClearLocalCMS /CMSName:mb100ccr
2. Verify with Cluster Administrator that all cluster server resources have been removed. These are
all of the steps needed; however, all of the configuration information must replicate through
Active Directory before all clients can access the SCR target.
Pages:
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509