Julian 39 Posted May 18, 2014 Share Posted May 18, 2014 I like to keep my data as safe as possible so, just in case there was ever some catastrophic issue at Evernote's data centre, I also have my local Evernote cache folder in my regular backup set which means that it gets backed up to various local destinations and also to my online backup services (Crashplan and Mozy). Unfortunately however the local cache folder seems to be structured such that all the actual note data is contained in a single "...\Databases\<username>.exb" file that is currently 934MB for my account. Whenever I make even a modest addition to my Evernote account such as adding a brief text note the .exb file is changed and so my online backup software sends the entire almost 1GB file up to the backup server. Would it be practical and would you (Evernote) ever consider restructuring the layout of the data in the local cache directory (a change that would be 100% invisible to users) so that the local <username>.exb file was broken into smaller chunks, maybe by replacing the <username>.exb file with a "<username>Exb" directory that contained "01.exb", "02.exb" etc files so that each individual .exb file was kept below a certain size and backup services would see less data changing when the user made even modest changes to his or her notes? Edit: Another option that just occurred to me that might be simpler to implement would be to keep the single "<username>.exb" file but have it only contain unique references to attachments rather than the actual data for the attachments. The actual attachments could then be stored in separate file chunks within a "<username" Attachments" sub folder. I suspect that would keep the main .exb file down to a quite manageable size and simple edits might not touch any attachments at all and, if they did, would probably only affect a single file within the attachments folder. Since an attachment can be up to 100MB in size a maximum file size within the attachments folder of 100MB would seem to make sense. - Julian Link to comment
This topic is now archived and is closed to further replies.