Mountability checks are failing with the following error:
ERROR 2014-11-03T08:05:02 [362] - Replay.Core.Implementation.Exchange.MountabilityChecks.ExchangeMountChecker () 11/03/2014-08:05:02.948 thread id: 5740 JET_errDbTimeTooOld, dbtime on page smaller than dbtimeBefore in record Error during opening database, in function DsmOpenDatabase
ERROR 2014-11-03T08:05:03 [283] - Replay.Core.Implementation.Exchange.MountabilityChecks.Jobs.DatabaseMountabilityCheckJob () Job 'Mountability check for database C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\MailboxDB\MailboxDB.edb' failed System.AggregateException: One or more errors occurred. ---> Replay.Core.Contracts.Exchange.MountabilityChecks.MountabilityCheckFailedException: Mail store 'C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\MailboxDB\MailboxDB.edb' is not mountable. Error: 'Error opening database. Jet returned error code -566, Error closing database, Error opening database. Jet returned error code -566, Database cannot be mounted' at Replay.Core.Implementation.Exchange.MountabilityChecks.Jobs.DatabaseMountabilityCheckJob.CheckDatabase() at System.Threading.Tasks.Task.Execute() --- End of inner exception stack trace --- ---> (Inner Exception #0) Replay.Core.Contracts.Exchange.MountabilityChecks.MountabilityCheckFailedException: Mail store 'C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\MailboxDB\MailboxDB.edb' is not mountable. Error: 'Error opening database. Jet returned error code -566, Error closing database, Error opening database. Jet returned error code -566, Database cannot be mounted' at Replay.Core.Implementation.Exchange.MountabilityChecks.Jobs.DatabaseMountabilityCheckJob.CheckDatabase() at System.Threading.Tasks.Task.Execute()<---
# /* dbtime on page smaller than dbtimeBefore in record */
In summary, there is a log buffer held within memory on the production machine and to help reduce IO on the system's disks. Certain events such as failover or a large number of job processes to the EDBs will flush this buffer to disk. This processes details that transactions of the EDB are first stored in memory and then triggered to commit to the disk by using the Log Writer process.
dbTime is to be seen as a counter rather than the actual timestamp of a transaction log commitment. When new logs are written to disk a unique database time is created in reference to that log creation time. During a disaster recovery scenerio the dbTime referenced to look for information regarding if the logs had been replayed or not.
If the Exchange server was just restored and the new incremental recovery points are throwing this error, it is advised to snap and transfer a new base image to recreate the new recovery point chain.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center