thanks, I fixed the text, it will appear in the next release.
> - database.backup
> - database.data
> - database.properties
> - database.script
Exactly these 4 files and
> - thumbnails -subfolder
otherwise the thumbnails will be rendered again which can take
> - database.log
is a temporary file created by HSQLDB.
> - ImageMetaDataViewer.lck
That's JPhotoTagger's lock file and shall avoid running
multiple instances at the same time (you will see a warning
if you are starting JPhotoTagger if the lock file exists).
> So by moving above mentioned files/folders to a location on my hard
> drive, that I regularly backup onto external hard drive, I should have
> all vital metadata and information backed up? (I should probably
> export and backup also Keywords tree regularly, so I won't lose
> hierarchical relationships of my keywords?)
The database only reflects the XMP metadata: If you edit something, it
will be written first into the XMP sidecar file(s) and second into the
database. If the database crashes or gets lost (e.g. hard disk crash)
or you delete it, you can get back all metadata via "File > Scan
Folders" or choosing folder by folder in the folders register.
JPhotoTagger can be executed on different computers with different
file systems, e.g. without drive letters from a Unix system: After
reading e.g. a network attached folder with images plus XMP, it scans
the XMP and stores into it's local machine dependend database all
metadata existing in the XMP (keywords, descriptions etc.). If you
have e.g. a NAS, you can edit metadata onto your laptop and if
JPhotoTagger onto your desktop PC scans the NAS folder, it will
see/find new/updated metadata.
The database is *not* to be intented for sharing, it may work, but
it's not guranteed, if 2 machines accesses the same database at
the same time it *will* be damaged (Windows usually forbids that
through it's internal file locking but under Linux you can do that).
All other data stored in the database should be exported from time to
time via "File > Export > JPhotoTagger Data" so that it can be restored
if the database get's lost, it's not into the XMP. And this is a
way to share keyword trees etc. on different computers or with
different users. See
for what is stored into the database
> But by regularly backing up all database.* files + thumbnails-
> subfolder + keywords tree, I don't have to do whole re-import through
> XMP sidecars, that will probably take rather long time, if one has
> tens of thousands of files in his catalog. Have I understood this
Keyword trees are only an input helper (appling keword +
it's parents with "one stroke"). Other example: Synonyms having
support functionality (finding the same under different
names, e.g. if your friend is stored as "Patrick Miller"
and you will find him through the keyword "Pat" but
you don't want to store that keyword into XMP).
> Of course I should also backup all my media files and their associated
> XMP sidecars files, that can be used to re-import all metadata, if my
> database gets corrupted/deleted for some reason.
It can't be recommended and repeated enough: Images plus XMP
should backed up regulary, *every day*. Good backup programs
(e.g. Free File Sync under Windows, rsync under Linux)
backing up only new/modified files, so the process is not too
time exhausting. That applies multiple times to best backup
programs storing multiple versions (e.g. for restoring every
day of the last week/month).
And this was an importand reason for JPhotoTagger's
decision not to write XMP into the files: The backup is *much*
faster and saves a lot of space: A huge image, e.g. a
high resolution RAW file or 48 Bit TIFF file takes 1000 times
more space than a small XMP text file and if you have a 3th.
backup "ensurance" like me - high Quality DVDs (4 GB Verbatim
Archival Grade) - time and costs are important.
Yes regarding the image metadata (keywords etc.) the database will be
fully re-created from the XMP sidecar files.
But also much that makes working easier is stored in the database:
Keywords tree, Favorite Folders, Programs to execute, Automatic Tasks,
... This data can exported and re-imported via "File > Export (Import) >
JPhotoTagger Data". That should be done from time to time, it creates
(small) XML text files. And the text file Settings.properties contains
some other user specific data.
With the current version 0.21.0 I added 2 other export items (User
Defined File Types and Word Collections).
> 2. If you wan't to save some time in the case your thumbnails folder
> gets deleted for some reason, you should backup it from time to time.
> But thumbnails can be recreated when needed. The process is however a
> bit slower than reimporting all metadata from XMP sidecars.
Yes. Creating thumbnails usually is much slower than reading metadata
from the XMP files. But if deleted, the thumbnails will be created
automatically on demand.
> 3. Because NO keyword hierarchies, synonyms and other additional data
> is stored inside database, this data SHOULD be exported and backed up
Yes, see obove.
> 4. Media files and their XMP files are the MOST important thing to
> backup regularly.
Yes. And a backup of these files should be done automatically not e.g.
by dragging them onto a backup drive, but using programs such as Free