In DT3, I today decided to move my database from unencrypted to encrypted.
I created a new (encrypted) database, and then simply drag/dropped all of my Groups from a to b.
Afterwards, I saw in the log a number of error messages “Insufficient disk space to import file(s)”
However, in the UI, the items are gone from a (unencrypted db) and do not exist in b (encrypted)
I ran a File > Check File Integrityt and found 6,000 orphaned files, which might be the items in suspicion. I can’t easily confirm because all of my grouping/tagging appears to have been lost.
Appreciate any pointers if there’s any way to restore my prior state?
(A good answer here would be to restore from last nights databse backup however, that’s not an option as I was in the process of getting ready to START doing daily backups. A day too late.)
Have done further research, it looks like the “Orphan files” are what I need.
So I have the data, but now my metadata is in a bad state.
For every orphan file, I have (a) an entry in the database that shows “File Missing”, and (b) an entry for the file, in an “Orphan Files” group.
I’d appreciate any thoughts on how to automate a reconciliation. E.g. I could just delete the metadata entries that show “File Missing”. But I’m not sure how to do that. They are scattered across several groups, and intermixed with valid files.
Afterwards, I saw in the log a number of error messages “Insufficient disk space to import file(s)”
And how large did you make the encrypted database?
I ran a File > Check File Integrityt and found 6,000 orphaned files, which might be the items in suspicion. I can’t easily confirm because all of my grouping/tagging appears to have been lost.
Appreciate any pointers if there’s any way to restore my prior state?
It’s very likely you’ll have to rebuild by hand. You did the check on the source database?
PS: It would be a File > Verify & Repair Database.
I ran a File > Check File Integrityt and found 6,000 orphaned files, which might be the items in suspicion. I can’t easily confirm because all of my grouping/tagging appears to have been lost.
Appreciate any pointers if there’s any way to restore my prior state?
(A good answer here would be to restore from last nights databse backup however, that’s not an option as I was in the process of getting ready to START doing daily backups. A day too late.)
I hope the next thing you do is run out to the store and get a sufficiently large external hard drive, then doing nothing else until you’ve got your local backups done and set up to run periodically.
Bummer, but that’s what I was expecting based on the past couple hours of work. Thanks.
I’m a few months into aggregating all my old content from Evernote (primarily) and other sources. The recommended size was 1 GB which felt outrageously large to me, so I reduced it to 100 MB. Clearly that was an error.
This is on a work MBP and I realized last night that that machine doesn’t do local drive backups, so I have to do backups manually. Was in the process of setting all of that up when this happened.
By way of feature feedback - would have been nice if DT had left the originals in the source DB when they were unable to be moved to the target, rather than stranding them as orphans with broken metadata.
Lesson learned though: check the target size is sufficient before moving via drag and drop.
Is there anyway to bulk find/delete all the “File missing:” entries?
I tried searching for “File missing:” (came up empty) and also looked to see if there was a way to filter the list by “file missing” as metadata, both ideas came up empty.
I’m reasonably confident that for every “File missing:” entry I have the corresponding file, it’s just been orphaned. I feel like I could live with just deleting the entries that go nowhere and having the files.
[UPDATE] Have searched the forums and it appears the answer to this is no. So, I guess I need to get to work manually finding and deleting the ~6,000 file missing records.
Thanks for that tip. The “Rebuild Database” item is grayed out in my File Menu. I’ll do some research to figure out why that might be the case.
Separately, I hope we capture the feature feedback on this one. On Mac Finder, or Windows Explorer, or my NAS software, or any other management app I’m familiar with, if you Move via drag/drop and the target is full, it just stops moving and leaves the source items intact. It’s been a awhile but I’m pretty confident the same is true for a Command Line “mv” command in Unix/Linux. It’s unusual in my experience for the source items to be removed and orphaned as they have been in this case just because the destination ran out of space.
