Exchange 2019 remove recovery database

Susan Dodds 191

Exchange 2019

Due to reasons, I created a recovery database and ended up not needing it.

I got to the point creating the recovery database and doing a soft recovery.

Is there anything I need to do to stop this recovery process before deleting the database to stop Exchange from trying to continue the recovery process? I don't want event viewer filled with errors of it still trying to do the recovery process and wonder where the database is.

Thanks

Mike Hu-MSFT 3,275 Reputation points Microsoft Vendor

2024-09-09T07:59:49.2433333+00:00

I am glad to know that the issue has been resolved, please mark the helpful replies as answers, this will make answer searching in the forum easier and be beneficial to other community members as well.

1 answer

Mike Hu-MSFT 3,275 Reputation points Microsoft Vendor

2024-09-02T08:14:08.58+00:00
Hi,

Welcome to the Microsoft Q&A platform!

To delete the recovery database and stop any associated processes, follow these steps:

Open the Exchange Management Shell and run the following command to dismount the recovery database:

Dismount-Database -Identity <RecoveryDatabaseName>

After dismounting, you can delete the recovery database using the following command:

Remove-MailboxDatabase -Identity <RecoveryDatabaseName>

Make sure there are no active recovery processes running. You can check the event logs for any ongoing recovery operations. If the recovery database is dismounted and removed correctly, you should not see any related errors in the Event Viewer.

Please feel free to contact me for any updates. And if this helps, don't forget to mark it as an answer!
Please sign in to rate this answer.
Susan Dodds 191 Reputation points

2024-09-03T21:52:05.6866667+00:00

I now have events saying:

The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.

Database: Missing database (****)

Error: Database '**' doesn't exist.

Andy David - MVP 147.5K Reputation points MVP

2024-09-03T23:41:40.6+00:00

Restart the service to clear that.

Susan Dodds 191 Reputation points

2024-09-04T03:46:29.96+00:00

Error persists after restarting the replication service.

Mike Hu-MSFT 3,275 Reputation points Microsoft Vendor

2024-09-04T07:25:11.7766667+00:00

I think you can use the Get-MoveRequest and Remove-MoveRequest cmdlets to check and clean up any active requests.

Get-MoveRequest | Remove-MoveRequest

Susan Dodds 191 Reputation points

2024-09-05T03:42:50.6633333+00:00

Error persists after cleaning up completed move requests.

Mike Hu-MSFT 3,275 Reputation points Microsoft Vendor

2024-09-05T09:32:25.24+00:00

Restart all Exchange services to ensure any in-memory references are cleared.

Get-Service | Where-Object {$_.DisplayName -like "Microsoft Exchange"} | Restart-Service*

Susan Dodds 191 Reputation points

2024-09-08T05:20:14.78+00:00

Rebooting the server entirely seems to have cleared the error.

Amit Singh 4,896 Reputation points

2024-09-09T06:54:55.2766667+00:00

PS-Regularly back up your Exchange environment and its configurations to prevent data loss and facilitate recovery in case of similar issues.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Exchange 2019 remove recovery database

1 answer

Your answer