I'm trying to find a way to import some older backup files that are several gb in size. I don't want to move to Bear although on desperately needing access to one particular backup exceeding 1gb, I used Bear to open the file and retrieve the data. Bear is NOT a solution to my problem as its handling of clipped pages for example is problematic. Also Bear has issues with enex files that exceed 2Gb. I do not want to go near other notes solutions because their privacy policies are an issue and I handle sensitive material. So Evernote on Google servers and Bear on Apple servers are the only two options for me.
So what am I left with?
The ideal solution would be to construct a pgrm to breakdown the large enex files into sub 200mb segments and import them. Does such a script exist?
I created a local notebook and tried to drag and drop the enex file into it but with no luck.
I do hope that I'm missing some simple solution here that I just have not encountered yet. I can understand the need to manage data block sizes and volumes of sync traffic etc for such a large platform etc, but what would be the point of facilitating backups of notes/notebooks exceeding the new data limits meaning that they can never be reimported?
Idea
Pat @ChildWatch 3
Hi
I'm trying to find a way to import some older backup files that are several gb in size. I don't want to move to Bear although on desperately needing access to one particular backup exceeding 1gb, I used Bear to open the file and retrieve the data. Bear is NOT a solution to my problem as its handling of clipped pages for example is problematic. Also Bear has issues with enex files that exceed 2Gb. I do not want to go near other notes solutions because their privacy policies are an issue and I handle sensitive material. So Evernote on Google servers and Bear on Apple servers are the only two options for me.
So what am I left with?
The ideal solution would be to construct a pgrm to breakdown the large enex files into sub 200mb segments and import them. Does such a script exist?
I created a local notebook and tried to drag and drop the enex file into it but with no luck.
I do hope that I'm missing some simple solution here that I just have not encountered yet. I can understand the need to manage data block sizes and volumes of sync traffic etc for such a large platform etc, but what would be the point of facilitating backups of notes/notebooks exceeding the new data limits meaning that they can never be reimported?
Kind regards, Pat
Link to comment
2 replies to this idea
Recommended Posts
Archived
This topic is now archived and is closed to further replies.