Event 628 ....Exchange | database skipped over non-visible nodes | widening online maintenance window.

Question

Hello Everyone,

We received the following Event on our Exchange Server 2013 [Cumulative Update 11 (CU11) 15.0.1156.6].

Alert Detail: Application log generated Warning Event 628 on SERVER.root.ctc
For more information see http://www.eventid.net/display.asp?eventid=628&source=ESE

Log: Application, Type: Warning, Event: 628
Event Time: 08:10:18 AM 5-Feb-2021 UTC
Alert Sent: 2021-02-05 00:10:52Z
Source: ESE
Computer: SERVER.DOMAIN.local
Username: N/A

Description: Information Store - Staff2 (8788) Staff2: Database ''''E:\ExchangeData\ExchangeMailboxDatabases\Staff2\Staff2.edb'''': While attempting to move to the next or previous node in a B-Tree, the database engine skipped over 10987 non-visible nodes in 30 pages. It is likely that these non-visible nodes are nodes which have been marked for deletion but which are yet to be purged. The database may benefit from widening the online maintenance window during off-peak hours in order to purge such nodes and reclaim their space. If this message persists, offline defragmentation may be run to remove all nodes which have been marked for deletion but are yet to be purged from the database.
Name: PseudoIndexMaintenance_479
Owning Table: PseudoIndexMaintenance_479
ObjectId: 396902
PgnoRoot: 491035
Type: 2
Unversioned Deletes: 2
Uncommitted Deletes: 0
Committed Deletes: 10985
Non-Visible Inserts: 0
Filtered: 0

I understand that this can be due to the database size, and insufficient time to complete the nightly maintenance plan. Can you tell me what the correct way is to increase this available time?

Thanks in advance.

Regards,
Rudy

Answer 1

Do you have backups or anti-virus scans running at the same time? that's typically the culprit. Rescheduling or spacing those tasks out is usually a better solution.

You may still see these regardless, so if its an ongoing issue, I would also consider scaling out and creating smaller databases if possible as well.

Answer 2

Hi @Rudolf Amarlapudi ,

According to the description of this event 628, it seems be related to the maintenance of database.

Based on my research, I found two parameters/settings to configure the maintenance of database: "Maintenance schedule" and "Enable background database maintenance (24 x 7 ESE scanning)"(Manage mailbox databases in Exchange 2013).

However, except the paramter "-MaintenanceSchedule"(It's also the setting "Maintenance schedule" in EAC), there seems no other parameters to specify the maintenance period(More details about this parameter: Set-MailboxDatabase), and this parameter is only available in Exchange 2010(It's deprecated in Exchange 2013).

Therefore, if this error persists, as said in the event: "Offline defragmentation may be run to remove all nodes which have been marked for deletion but are yet to be purged from the database.", I think you could perform a defragmentation for this database with eseutil(Because a database defragmentation could cause a corrupted issue on database, before defragmenting, please backup your database): Defragmentation of the database with ESEUTIL
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.