Register / Login | Desktop view |
That's correct.Mark Gerber wrote:Some of the programs I use recommend their databases not be backed up while the program is running. Specifically, I'm thinking of DEVONthink Pro, PowerMail, and SOHO Organizer (which uses OpenBase).
Also correct. This was discussed some time back in the "QRecall and CoreData" thread.... And, of course, I'd like to capture these files a few times during the day. It's my impression the potential for damage is due to the fact that these databases needed to be closed before copying, otherwise an incomplete file will be written.
Not at the moment, but I have plans to address this (and similar problems) in an upcoming release.For this purpose, does QRecall do anything different in capturing quanta so I wouldn't have to be concerned about quitting the program to ensure a complete, undamaged capture?
I wanted to do one for rolling merges too, but it needs some wickedly complicated animation and my Final Cut Express skills weren't up to it. If I get some time to extend the series, that will be the first one I attack.By the way, I just found the screencasts on your home page. They are well done and present the information very clearly.
I look forward to seeing more, in particular, one that clarifies the rolling merge options.
Oops. Now I wonder if what you wrote is what I'm remembering. Should have searched the forums a little better than I did.James Bucanek wrote:Also correct. This was discussed some time back in the "QRecall and CoreData" thread.
That would be a welcome solution. But until then it sounds as if I will have to exclude any file that might have an open database in a folder I intend to backup (I work at home, my hours aren't regular, and I don't know if I can be disciplined enough to quit those programs that might fall into this category).To specifically address the issue of databases, I'm planning a new filter option that will ignore a folder full of files if any of those files are currently open for modification (write access). The capture would always be "safe" in that the capture would only occur if all of the files are closed.
I would lean more towards ensuring that you get at least one good capture from time to time. One way of doing that would be to schedule a capture that occurs when you log out. Logging out would then guarantee a "clean" capture of all of your databases.Mark Gerber wrote:But until then it sounds as if I will have to exclude any file that might have an open database in a folder I intend to backup (I work at home, my hours aren't regular, and I don't know if I can be disciplined enough to quit those programs that might fall into this category).
I'm not aware of any.Is there someplace a list of those applications using CoreData?
Is that possible?Or am I perhaps being too paranoid about this problem?