I have this problem since about 23rd December on a 2012 R2 Essentials Server.
Using a VSS backup application (Macrium Reflect 5.3).
It sometimes works now, but mostly fails to backup. I have rebooted etc.
What is happening, is that during shadow copy creation, Active Directory database engine ESENT seems to switch to using the shadow version of the active directory database (ntds.dit), but then decides that the edb.log has range checksum mismatches.
The system is running fine but will not do backups! Maybe 1 in 20 will succeed.
Shadow creation starts, then I see these events:
Information09/01/2016 00:22:11ESENT102General
lsass (588) The database engine (6.03.9600.0000) is starting a new instance (1).
Information09/01/2016 00:22:11ESENT216Logging/Recovery
lsass (588) A database location change was detected from 'C:\Windows\NTDS\ntds.dit' to '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy28\Windows\NTDS\ntds.dit'.
followed by:
Information09/01/2016 00:22:11ESENT300Logging/Recovery
lsass (588) The database engine is initiating recovery steps.
Information09/01/2016 00:22:11ESENT216Logging/Recovery
lsass (588) The log range read from the file "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy28\Windows\NTDS\edb.log" at offset 9007104 (0x0000000000897000) for 4096 (0x00001000) bytes failed verification due to a range checksum mismatch. The expected checksum was 0 (0x0) and the actual checksum was 9442647854575 (0x89689abcdef). The read operation will fail with error -501 (0xfffffe0b). If this condition persists then please restore the logfile from a previous backup.
Error09/01/2016 00:22:12ESENT465Logging/Recovery
lsass (588) Corruption was detected during soft recovery in logfile \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy28\Windows\NTDS\edb.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 2199 (0x00000897). This logfile has been damaged and is unusable.
Error09/01/2016 00:22:12ESENT454Logging/Recovery
lsass (588) Database recovery/restore failed with unexpected error -501.
I'm not sure if it is supposed to switch database location to shadow copies during shadow creation? Does anybody know?
I've exhausted all of my Googling powers now, hence the post! I did wonder if it was a 4kb issue or something. It's a Lenovo TS140 server, 2012 R2 Essentials, 2x 1tb SATA on Intel C600 RSTe RAID1 (motherboard/soft/fake raid). The volume is reported as 4kb physical and 512 logical (i.e. 512e), which is about the norm nowadays.
Grateful of any help!