I have been using an encrypted sparse bundle disk image of my EF library on Dropbox (1.0.28) on two different computers (both are OS 10.6.7) for a while now and it seems like every few months the EF library gets corrupted. I end up setting up a new library and dragging in the library records to recover my library. I know that you have to be careful when using an EF library with Dropbox but I am wondering what my most likely mistake has been.
Here is my usual procedure:
Use the EF library at work on my office computer. At the end of the day, I always chose the Close & Lock command and then I close the EF program. I am positive that I always do this. I leave the computer on all the time.
At home, my laptop is typically on all the time too but is in sleep mode with the cover closed. I open the laptop and awaken it. I think that I am pretty careful to allow Dropbox files to sync before opening the EF library, but I am wondering if maybe once in a while I forget to do this. I have a alias setup in the dock to open the EF library in Dropbox by clicking on it - so maybe that makes it more likely that I might not check to see if the files are done doing the sync.
When the library become corrupted, it very quickly becomes unusable. Often it will not open up at all. Restoring with Time machine seems to fix it on the computer I am working on, but it runs very slowly and is probably corrupt in some way. It usually still has problems in the other computer too. I have other forms of backup in addition to Time Machine that I can use too.
Does it seem likely that my mistake is as described in #2 above - opening the library before syncing has finished? Is that always fatal?
What is the best way to recover from the case of the corrupted library - is it best to start with a new library as I have been doing?
Would there be an advantage to using the sparse disk image format instead of the sparse bundle disk image or not to use a disk image at all when using Dropbox? I thought that the sparse bundle disk image was the preferred way to go when using Dropbox but I am not sure if that applies to this particular issue of corruption.
Thanks for any suggestions.