Jump to content
Updates to the Evernote Discussion Forums! Read more... ×

Denis L

Member +
  • Content Count

    49
  • Joined

  • Last visited

Community Reputation

20 Neutral

2 Followers

Recent Profile Visitors

1,384 profile views
  1. Hello, New release of Backupery for Evernote is here. What's new: Backup retention policy (allows to set how many backup snapshots the app keeps on a backup destination) Ability to set time of a day when backup is scheduled Manual backup mode. It allows to perform backups manually when needed without being tied to a specific backup schedule Ability to cancel running backup Added support for official Evernote client installed from Microsoft Store (applicable for Windows edition) Works similar for Windows and Mac Lots of bugs were fixed More features coming soon! Download it here: https://www.backupery.com/products/backupery-for-evernote/ Windows app: Mac app: Here is a bit more info with screenshots: https://www.backupery.com/backupery-for-evernote-9-is-available/
  2. Thanks for your assistance! Got it. Will fix that for the next release. It looks interesting! I didn't know about this feature of Evernote client. Saving single EXB file looks much more simple than exporting a whole account to ENEX. It's something I should research thoroughly. Thanks for pointing me to this direction.
  3. Yes, you are right, there is no note ID information inside the ENEX export. What I'm thinking about is to read database in order to find ID of the exported note. It seems we have enough information in ENEX file at the export time to find out the ID of the note. Then we should store it somewhere just to be able to track the changes further. Basically it's a theoretical idea so I'll do some research. Thanks so much for the feedback. I've reviewed it carefully and took much of it into consideration. Actually the feedback is so essential since it is based on what a real user feel is important, which often can be very different from what I think is important 🙂 Hope many of the requirements will be available in the next version of the app, so I'll keep this thread updated!
  4. Thank you very much for your comments! We're currently working on the retention policy feature, hope it will be available soon. Basically it will work the following way - a user sets the maximum number of backup sets that the tool should retain so the obsolete backup files are deleted automatically. You are absolutely right. Currently the tool doesn't provide an import option so users have to roll their own import routine based on Full or Incremental backup types. If we are talking about full backups the import process basically looks clear, except the possible large file import issue. Though I hope it can be solved by splitting a large ENEX file into small safe files. If we are talking about incremental backups it might be not an easy task to restore the data to the desired state (the issues described above by Gazumped take place). So yes, we definitely should improve the restoration for incremental backups. I'm currently thinking about the following option: what if when a user requests restoration from incremental backups the tool would automatically glue the first full backup with the following incremental backups? So if a user requests restoration to some date in the past then the tool produces a single ENEX file that contains the full backup to the desired date. Well, as we already noted, importing a full backup looks easier than importing incremental backups. I'll investigate this option.
  5. Thanks for the explanation. Yes, it was a problem with ENScript.exe tool on Windows that led to sporadic hang of the export process for large notebooks. I hope the issue is gone now but I'm still observing export logs in my test lab just to be informed if the problem occurs again.
  6. Thanks for the information. Yes, probably a very large file is the reason of the problem so the system just can't handle it correctly and import fails. I've just thought that since an ENEX file is basically an XML file so it can be broken up into small parts (other ENEX files) automatically during export process. In this case restoration would be a little more complicated (we would need to import several ENEX files instead of large one), but I think it's worth the efforts. What do you think on this?
  7. We haven't experienced any issues restoring a notebook from an ENEX file. Probably the notebooks weren't large enough though. Just for our records - may I ask what the platform (Windows or Mac) was and the rough size of the notebook was?
  8. Hi gazumped, I'm sorry for not following-up on this. The export hang issue took much time since we can't reproduce the issue in our lab and so base our research on responses from our users who stumbles upon the problem. As for now, we haven't experienced the issue since Evernote 6.9.6.6729 (at the time of writing the current version is 6.11.2.7027 (307027)) so I hope the issue is gone. However, I'll continue our observation and will research it further if necessary. As for slowing laptop too much - I can confirm it's really the issue now, so the next version of the app will have a fix that allows to run an export process with a custom priority so it doesn't hurt computer performance. I will update this thread when the new version is out. sorry I'm afraid I don't get it. Do you mean the app should back up the database before starting the export process?
  9. You may also want try Backupery for Evernote tool: https://www.backupery.com/products/backupery-for-evernote/ One of the export formats the app provides is ENEX so the notes can be easily imported back if necessary. However, please note, the app gravitates towards to notebook-oriented export rather than individual note-oriented export so if you need to restore a particular note, you have to restore (at least temporary) the whole notebook which contains this note.
  10. Denis L

    Deleted notebook which i cant recover??

    Have you checked Evernote Web? If you haven't synced your Evernote Windows app then the note can be there.
  11. Just an update on the issue that may prevent a large notebook from backing up. (As you probably remember, some large notebooks can't be exported successfully with no apparent reason) I've got the reply from Evernote Team - they're aware of this issue and working on a fix to be scheduled in a future release, but they don't currently have an ETA for when it will be resolved. So, hope it will be fixed in the next release of Evernote client. Meanwhile, I'll try to create some kind of workaround for the issue.
  12. Hi gazumped! Thanks so much for checking out the tool and for your feedback. It works the following way for the incremental backup: if the app sees there is no previous notebook backup at all, then it makes full notebook backup, i.e. exports all the notes from the notebook. That is why the first incremental backup is actually the full one. If some previous notebook backup exists, then the app exports notes that were added or updated after the latest backup. Here is a quick example: Say I have a notebook called Notebook1 and run the app for the first time at the 1st of July 4.30 A.M. Since there is no previous backup, then the app makes full backup of the notebook and creates the single enex file in Notebook1 directory: <StoragePath>\Notebook1\2017_July_01_04_30_00.enex Let's say the next run is at the 3rd of July 10.30 A.M. Since the previous backup already exists the app exports all the added/updated notes that were introduced between the 1st of July 4.30 A.M. and the 3rd of July 10.30 A.M., so the backup directory contains: <StoragePath>\Notebook1\2017_July_01_04_30_00.enex <-- the first backup (full backup) <StoragePath>\Notebook1\2017_July_03_10_30_00.enex <-- added/updated notes after the 1st of July 4.30 A.M. till now (i.e. till the 3rd of July 10.30 A.M.) On the next run (say at the 5th of July 11.00 A.M.) it exports added/updated notes between the the 3rd of July 10.30 A.M. and the 5th of July 11.00 A.M. In fact, I'm began working on it a short time ago. I can't provide ETA for now, but I think it will be ready for the following couple of releases. Actually it is a frequently requested feature, so it's already on our roadmap. I think I got your idea, but just to double-check: you wish to have the ability to remove backup files over x days old without entering each of 100 directories and manually delete each file, right?
  13. I'll keep you updated on the progress!
  14. Denis L

    ENScript export issue

    Hi there! Hope someone from Evernote can help. We've discovered strange behavior of ENScript.exe tool. Sometimes during the export of notebooks ENScript.exe hangs with no apparent reason. The problem arises sporadically, so we still haven't found clear steps to reproduce the issue. Trying to run the same export after some time may or may not help. The problem arises on different machines and different Evernote clients. Command line is: ENScript.exe exportNotes /q "notebook:\"MyNotebook1\"" /f "C:\test1.enex" names of the notebook and enex file may differ, I've just simplified them. Here are the examples: ======================= PC1/Evernote account1 ===================== Windows version: Microsoft Windows NT 6.2.9200.0 x64 (Windows 8) Evernote Client version: 6.6.2.5173 Tried to export all notebooks from the account one by one several times, the first 2 times all notebooks were exported without any problems except the single notebook for which the export never ends (have been waiting for more than 5 hours) and the generated ENEX file is always 1.8 GB. On the third run (after a couple of days) the export for this notebook completed successfully (it took about 1.5 hours) and generated ENEX file is 19 GB. All other notebooks are exported all the times without any problems. ======================= PC2/Evernote account2 ===================== Windows version: Microsoft Windows NT 6.1.7601 (Windows 7) Service Pack 1 x64 Evernote Client version: 6.5.4.4720 Tried to export all notebooks from the account one by one several times, the problem occurs for a single notebook only, each time export never ends (have been waiting for more than 5 hours) and the generated ENEX file is always 5,9 GB. All other notebooks are exported without any problems. ======================= PC3/Evernote account3 ===================== Windows version: Microsoft Windows NT 6.1.7601 (Windows 7) Service Pack 1 Evernote Client version: 6.4.2.3788 Tried to export all notebooks from the account one by one several times, the problem occurs for a single notebook only, each time export never ends (have been waiting for more than 5 hours) and the generated ENEX file is always 104.6 MB. ================================================================ Please advice, Thanks!
  15. Hi there! Here is a quick update on the problem that leads some notebooks are skipped from the backup. As you probably know, at some step of backup process the app uses ENScript.exe (https://dev.evernote.com/doc/articles/enscript.php#enscript) tool to perform export of notebooks. We've discovered that the tool hangs sometimes exporting large notebooks (> 2GB) with no apparent reason. The problem arises sporadically, so we still haven't found clear steps to reproduce the issue, but I suppose this is because of some kind of notebook "locking" since trying to run the same export after a few hours often helps so the backup completes successfully. I'll report the issue to Evernote, hope they shed some light on the issue.
×