Forum Discussion

justletmelogin50's avatar
justletmelogin50
Brass Contributor
Dec 13, 2024

DatabaseCopyActivationDisabledAndMoveNow issue

Hey all,

Some info first:

Two Exchange 2019 CU14 in a DAG on Server 2022

Two mailbox databases

I just installed the latest SU on the second server and when it came time to move the Active databases back I got this error:

Server "exchange1" is enabled for DatabaseCopyActivationDisabledAndMoveNow. Moving databases to such servers may be ineffective because the system will automatically attempt to move again as soon as a healthy copy is detected.

I thought I had already set that back to False so I checked:

Get-MailboxServer Exchange1 | Format-List DatabaseCopyActivationDisabledAndMoveNow

DatabaseCopyActivationDisabledAndMoveNow : False

I ran the command again to set it to False just in case, but I still get the same error when trying to move the databases.  The databases show as Healthy on Exchange1, and Exchange is functioning fine otherwise.

I cannot see anything obvious in the event logs.

Does anyone know what the issue might be?

thanks

Justin

 

EDIT: Bah! Nevermind, it took over a half hour but I was just able to move the databases back, and everything appears fine.

1 Reply

  • MarissaMa's avatar
    MarissaMa
    Iron Contributor

    1. Check replica health status

    powershell
    Get-MailboxDatabaseCopyStatus -Identity “DB01\SERVER02” | FL Status,ContentIndexState
    If the status is Failed, run the repair command:

    powershell
    Update-MailboxDatabaseCopy -Identity “DB01\SERVER02” -CatalogOnly
    2. Force the copy to be reactivated

    powershell
    Move-ActiveMailboxDatabase “DB01” -ActivateOnServer “SERVER02” -SkipClientExperienceChecks
    3. Verify

    powershell
    Test-ReplicationHealth -Identity “SERVER02” -SkipClientExperienceChecks
    Get-MailboxDatabaseCopyStatus -Identity “DB01\SERVER02” | FL ActivationSuspended
    Confirm ActivationSuspended is False for successful repair.

Resources