Another Backup Plugin for KeePass Activity
Brought to you by:
bill-rubin
Activity for Another Backup Plugin for KeePass
-
Bill Rubin posted a comment on discussion Help
Good point! Investigating the situation more deeply, I found the following: The ABP code path that causes successful deletion and renaming is the same code path with the same parameters as that which causes the invalid handle response. ABP has no code for deletion or renaming. Instead, ABP calls back to KeePass through the plugin interface to perform these functions. The deletion and renaming is encapsulated in a single plugin interface function called IKpFileTransaction::CommitWrite(). Based on...
-
JcB posted a comment on discussion Help
Thank you for your response. Your explanation seems reasonable, except that I do not understand how ABP can successfully delete the old backup file and rename the temporarry file on startup, yet cannot do the same thing immediately following the creation of the temporary file.
-
Short Answer: Based on your description, and my assumption that the problem is a Windows 10 bug, a temporary workaround is to replace ABP 1.12 with ABP 1.11. Long Answer: In all releases of ABP before 1.12, the backup file is written directly on top of any previous backup file to the same directory. This means that the old backup file is effectively deleted as soon as ABP begins writing the new one. With this simple design, there is a risk that if ABP never finishes writing the new backup file (such...
-
I am using KeePass 1.37 with ABP 1.12 on a Windows 10 system running the 1903 release, but this problem also occurs on the 1809 release. I start KeePass with a shortcut containing the command line: "C:\Program Files (x86)\KeePass Password Safe\KeePass.exe" C:\Users\thisUser\Keepass\Database.kdb /backup.path:"H:\KeePassDB\" Where H: is a USB drive. I have tried setting the backup.path to a directory on the C: drive just to see it that mad any difference, it does not. The first time I attempt to save...
1