Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
In recent months I have observed two instances of database corruption occurring during synchronization. In each case a local (source database) and network (sync target database) were simultaneously corrupted. The cases occurred on independent, physically remote installations, with entirely different databases. The corruption is rare, and seems to occur during events where KeePass normally executes flawlessly. Following is a description of the circumstances that are common to both instances of database corruption.
It is likely that corruption occurred when the trigger was activated by a reboot while the database was unlocked. My risk of data loss is small since both installations are backed-up regularly , but users who use sync as a form of backup could be at a higher risk.
In my mind, the notable feature of this error is that both source and target database are corrupted. This suggests that the corruption event occurred prior to saving either database, and corrupted databases were saved. This distinct from corruption occurring as a result of an interrupted save.
Did the corruption result in an unusable database or just an entry or two?
Did it change the database size significantly?
The databases were unusable. I did not check file size before I overwrote the corrupt versions.
Going forward I am running a test database alongside my production database. If the corruption happens again I'll be able to provide a sample database. However, the corruption event is very rare.