E2K10 – How for DAG Reseed


Need to reseed DB to another site, but fail for a few times using EMC. Below is the finding:

  1. Not use EMC for DB reseed, EMS please
  2. 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.

     

  3. Offline backup the active database and transfer the file to the passive node.

    . too complex and need the downtime as well

     

  4. 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

Reference

How to Reseed a Failed Mailbox Database Copy in Exchange Server 2010

http://exchangeserverpro.com/how-to-reseed-a-failed-mailbox-database-copy-in-exchange-server-2010

Don’t Reseed That Exchange Server 2010 Database!

https://communities.netapp.com/community/netapp-blogs/msenviro/blog/2011/12/01/don-t-reseed-that-exchange-server-2010-database

Performing a manual copy of a mailbox database in a DAG

http://www.misdivision.com/blog/performing-a-manual-copy-of-a-mailbox-database-in-a-dag

Advertisements
This entry was posted in Exchange 2010. Bookmark the permalink.

One Response to E2K10 – How for DAG Reseed

  1. jonsonyang says:

    after a few tries and troubleshooting, 3 days managed to reseed 8 DBs for MY2SG. Update as below:
    a. 10GB/30mins is up to 1GB/min. this is due to the DAG network configuration wrong, and all traffic was via MAPI nw instead of REPL nw. the solution is to combine the 2 REPL subnet into one under the DAG. the defaul setting does not work for REPL nw
    b. Run “-Databaseonly -DeleteExisitngFiles -ManulResume” only, then follow up Resume-xxx
    . without “-DatabaseOnly”, you can’t resume it, otherwise it will be still “FailedAndSuspent”
    . if run “-CatalogOnly” after “-DatabaseOnly”, the replicated DB will be gone !!! not know why?
    c. E2K10 version is SP2 + UR3
    d. will continue re-seeding other 12DBs for SG2MY later

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s