Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, August 2, 2018 1:24 PM
On Exchange 2016 I'm seeing Event ID 733 for source ESE, Online Defragmentation. It says the Online Maintenance Database Checksumming background task is not finishing and has been running for 83 days. Database is 120 GB. It is set for 24 x 7 ESE scanning. If I try to use the maintenance schedule instead I get an error that says "Your request couldn't be completed. Please try again in a few minutes."
Is it even possible to use the maintenance schedule instead of the background database maintenance or has that been deprecated? Would there be any advantage to it? If not, is there something I can do to get the task to complete? And is this something I should even be concerned about?
Thanks a lot.
Kenny
All replies (7)
Thursday, August 2, 2018 2:01 PM
Couple of things
1. Maintenance schedule is ignored now. So no its not possible to change the schedule
2. How big is the DB in question?
3. Do you have other databases that are finishing?
4. After the 733 event, can you see other events indicate that the scanning is completed? Like 735,736,737? If yes, you can safely ignore this event.
5. Filter the application log for ERRORS and CRITICAL events only and review to see if there is anything else occurring to that DB
6. Is this DB part of a DAG?
7. How often are you backing up this EDB and with what application/process?
Search, Recover, Export Mailboxes, Folders, Email, Contacts, Calendars, Tasks, etc. from Offline Exchange Databases (EDBs), On-Premise Exchange Servers and Office 365. Migrate/Recover direct from any offline EDB into any On-Premises Exchange Server, even cross version i.e. 2003 → 2007 → 2010 →2013 → 2016 → Office 365 with Lucid8's DigiScope
Thursday, August 2, 2018 2:13 PM
The DB is 120 GB. It is part of a 4-node DAG with all databases being between 120 and 140 GB.
None of them are completing.
I do not see any other errors or warnings related to the databases.
We back up nightly using Veeam.
Thanks
Kenny
Thursday, August 2, 2018 2:21 PM
- Whats your patch level of the servers and are they all the same https://technet.microsoft.com/en-us/library/hh435098%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
- Check your SYSTEM event logs for Critical and Error events & look closely at any disk related events
- Are these physical boxes or VM's?
Search, Recover, Export Mailboxes, Folders, Email, Contacts, Calendars, Tasks, etc. from Offline Exchange Databases (EDBs), On-Premise Exchange Servers and Office 365. Migrate/Recover direct from any offline EDB into any On-Premises Exchange Server, even cross version i.e. 2003 → 2007 → 2010 →2013 → 2016 → Office 365 with Lucid8's DigiScope
Monday, August 13, 2018 9:06 AM
Hi Kenny,
I'm just writing to check how's everything going? If you have any questions or needed further help on this issue, please feel free to post back. If 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.
Thanks for your understanding.
Best Regards,
Niko Cheng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Thursday, August 23, 2018 12:10 PM
This was resolved by just doubling the amount of RAM in the servers from 16 to 32. Seems to have resolved some other issues as well.
Thanks a lot.
Kenny
Thursday, August 23, 2018 3:37 PM
Great info, yeah Exchange loves memory!
Thanks for the update
Search, Recover, Export Mailboxes, Folders, Email, Contacts, Calendars, Tasks, etc. from Offline Exchange Databases (EDBs), On-Premise Exchange Servers and Office 365. Migrate/Recover direct from any offline EDB into any On-Premises Exchange Server, even cross version i.e. 2003 → 2007 → 2010 →2013 → 2016 → Office 365 with Lucid8's DigiScope
Friday, August 24, 2018 12:30 AM
Hi Kenny,
Glad to know the issue has been solved, 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. Thanks for your understanding.
Best Regards,
Niko Cheng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.