Need to reseed DB to another site, but fail for a few times using EMC. Below is the finding:
- Not use EMC for DB reseed, EMS please
EMS notes:. Log onto the passive node instead of the active node
. Run the update with the DeleteExistingFiles option : Update-MailboxDatabaseCopy -Identity DBName\ServerName –DeleteExistingFiles -ManualResume
But this may not fail as well due to the follow up reseeding of the content index
The best & safe arrpaoch is to reseed DB first, then the content index:
. Update-MailboxDatabaseCopy -Identity DBName\ServerName –DatabaseOnly –DeleteExistingFiles -ManualResume
. Update-MailboxDatabaseCopy -Identity DBName\ServerName –CatalogOnly
. How long to complete the reseed ? depends. For MY2SG = 10GB/30mins, too slow. If something wrong, have to reseed again, very time consuming.
Offline backup the active database and transfer the file to the passive node.
. too complex and need the downtime as well
Recommend solution found is:
. Create a new DB with all copies
. Move the mailbox to the new DB
. Remember to disable SecondCopy in the DB to speed up the mailbox moving, and enable it back later
How to Reseed a Failed Mailbox Database Copy in Exchange Server 2010
Don’t Reseed That Exchange Server 2010 Database!
Performing a manual copy of a mailbox database in a DAG