I've switched from SQLite to MariaDB on my local DigiKam machine (Windows 10)
- it's much faster now, BTW. Now I'm wondering what is the best way to
backup the database. With SQLite it was easy - just copy all the database
files to another (safe) location.
With MariaDB I'm doing the following and would like to know if this is good
I use HeidiSQL admin tool for this procedure to copy the DK database to my
local Linux server with MySQL installed:
1. Tools -> Export database as SQL
2. Choose the Output as my MySQL server and same database as on source
3. Select to create tables and "Delete + Insert (truncate existing data)"
4. Select the digikam DB on my local machine
5. Click Export and wait for process to finish.
So my questions are:
- is this procedure OK and will I be able to restore the database the same
way so digiKam will use it without problems (hope I won't need this )?
- what bothers me is the fact that on the destination server the tables'
properties are different after export than on the source (local machine),
for example there are different numbers of rows reported. Any ideas why that
Or does somebody have any other suggestions on how to easily backup the
I think you do need to wait for one of the Nabble team to assist.
However, in general my advice would be use a mail list archive as a read-only facility - after all the term "archive" implies it's a dead document for reference only. Use it as a way of checking on topics discussed before subscribing or as a way to avoid clogging a mailbox with a lot of mail in which you have no interest and only rarely have something to add to the conversation (and do that by email).
I've even seen cases where people want to email a Nabble archive so it can then forward the post to a mail list! Now that is weird!
Just a Volunteer Nabble Helper - because the nice folk at Nabble have helped me! GregHelp - Building a set of answers to Nabble FAQs.