i'm trying to make a database copy healthy, issued a manual seeding but cancelled it. now i can't issue further commands related to the index as the error messages says a seeding is in process. the active database is healthy but crawling.

how does one cancel an interrupted seeding?

Removing the new mailbox database copy should leave things just as they were before you started. Do you get an error message if you try to remove it, as per this Technet article ?

hi, as per the article, no i don't have any errors. DAG and active copy of the database are healthy.

if i remove this passive copy, and the active copy is crawling, will it affect the new database copy's index state?

It shouldn't, since the Microsoft Exchange Search service is running locally on each mailbox server holding a DB copy, updating locally the content index files (I don't have a link to a Technet article describing this though). However, once the copy is removed, you'll be left with your mounted DB, and the DB+content index files on the mailbox server that hosted the copy you just removed.

ok. i'll remove the passive copy, clean it up (remove the .edb and log files), then redo the copy.

before i remove the copy, i thought of resuming the databasecopy. however i got the below error message:

WARNING: A server-side administrative operation has failed. Couldn't resume the database copy because a database seed
operation is in progress. Either cancel the seed or retry later. [Database: DB01, Server:
server02.ACME.COM]

Can you try Update-MailboxDatabaseCopy DB\Server -CancelSeed ? According to the parameter description here, "The CancelSeed switch specifies whether to cancel an in-progress seeding operation."

• Proposed as answer by David Wang_Microsoft contingent staff 5 hours 43 minutes ago

when i removed the database copy (from EAC and then remove the files and folders associate with the database), and redo the databasecopy, the queue length started from where it left.

i was hoping the -CancelSeed would allow me to resume the database copy so that the queue length goes down. i believe the queue length will stay high until database copy is done?

Hi,

Please refer to Albert's suggestion to cancel an in-progress seeding operation.

More detailed information,please refer to the link:

https://technet.microsoft.com/en-us/library/dd335201(v=exchg.150).aspx

Regards,

David

hi,

not yet, since i removed the database copy from server02, and started a new database copy, i have to let the process finish first.