I keep getting the following
for an “encrypted database”
I have rebuilt it a few times, but I can’t find the verify option. How do I know if the rebuild succeeded? And where is the verify menu option?
See File > Verify & Repair Database…
But is there actually any space left? Encrypted databases are based on sparse images, the remaining disk space is shown in File > Database Properties
Space could be an issue. I forgot that encrypted databases were based on sparseimage.
Here is a screen shot of my database properties page. I don’t see an indication of remaining space and below that (for clarity ) is the information from DiskUtil for that sparseimage.
It says „5.5GB“ at the bottom (Total). Not sure what that means with a 2.01GB sparse image
Is this a sparse image that you created & mounted on your own? In case of an encrypted database (file extension .dtSparse) the screenshot should be slightly different, e.g. show the path of the database (not the one on the volume) and also the available disk space.
However, you could copy the database (Notes.dtBase2) to the desktop and try to rebuild & verify the copy.
The total size includes indexed items.
1 Like
So… the sparseimage may have been created a longtime ago, when my laptop was considered my main machine.
Now I use a MacStudio as the main machine and the Notes database is syncronised, by DT, between the two. On the MacStudio the Notes database is not a sparesimage and is 6.2GB in size. On my macbook, the Notes database is a sparseimage.
I just noticed that on the MacStudio the Notes database does not ask for a password. But when I start DT on the MacStudio it recieve a password request to unlock the Notes database on my Macbook. Presumably because DT is trying to mount it to complete a sync, initiated by the MacStudio.
Maybe the solution is to enlarge the sparseimage on my MacBook and see if the sync proceeds and completes?
Unencrypted on one machine, and encrypted on another. Do you actually need encryption on the laptop version? Is not the laptop’s disk/ssd already encrypted with Apple macOS “FileVault”? Would simplify things for you if this a viable option.
That’s one possibility, another one is to use an unencrypted database.
So. I removed the sparseimage. Rebuilt the database on the machine that didn’t use an encrypted database. And I am now trying to sync the rebuilt database across to the laptop. But it seems the sync is protected by a username and PW. See screen-shot. All my databases have this. Where did it come from? When and Where was it created?
That information had to be created by you. DEVONthink does not assign any such kind of data to a database.
1 Like
Yep. I am curious when, where and how I would have done that? Does it come from Syncing via DTG? Or is it only entered through that panel? Through the Database Properties Panel? On the Mac. I don’t recall explicitly adding it ( I might have these databases are a decade old ).
And why are those values different for each database, depending on the machine. For example in some places the database has user-name and password and the same database on a different machine has different values or no value at all.
Databases from DEVONthink 2.x can have a username and password set in the Database Properties as it was used as a simple lock for the databases then.
And yes, if you create a database in DEVONthink To Go, you can specify a username and password.
The user/password can be only changed by the user, neither sync nor automation can change it.
Thanks. I wasn’t sure when I hd entered those. Fortunately the UID/PW is very easy to retrieve. Thanks for that…
Bringing this full circle.
The errors were not with the sparseimage/encrypted DB (though I am sure eventually that would have been a pain point), they were with the unencrypted version, kept on the MacStudio. I repaired the database several times, verified and repaired it and eventually ended with a clean database on the MacStudio which I am syncing with the laptop.
I have abandoned - for now the encrypted databases on the laptop.
Encrypted databases should be as reliable as regular ones as long as there’s enough disk space (and unfortunately the amount of free disk space reported by macOS is not that accurate & useful anymore on the latest macOS releases). Therefore choosing a generous maximum size for the sparse image should avoid this.