Incremental backup and mtime

[snowman]

Hello,

I while ago there was a thread about the problem that openkm sets the mtime of repository file each night. I recently asked there for news. Because there were no answers then. I open up this as a new topic.
I think it is quite important to many people to be able to do incremental backups on the repository.

My symptom ist that openKM 5.0.3 - or whatever - is setting mtime of the repository files to midnight of that day. This happens without any user interaction. The system is up and running but not used for days. Addtionally, sometimes I see mtime of 7:43 the same day.
Any backup program - I use bacula - I know of refers to mtime for doing the backup. Basically, this way incremental backups do not work with openKM.
My question now is, what causes the mtime setting each night and how to turn it off. I cannot see any good reason for this behavior.

Best regards,
snowman

[pavila]

OpenKM document storage is build on Apache Jackrabbit. Maybe this question should be asked in the Jackrabbit mailing list. We actually make incremental backups with rsync and rdiff-backup and didn't notice any issue.

Every night a daemon process is launched to purge the orphaned files from the file datastore. Maybe this cleanup process modify the file mtime property.