View Single Post
Old 12-15-2017, 07:20 AM   #4
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
You might need some of the other database files, but cc.db is the main one.
If librariansync is working for you, then whatever it does to the database system is what you want to keep.

It need not be firmware specific - just back up a complete dump of the database.
Code:
cd /var/local
sqlite3 cc.db .dump >/mnt/us/collections.sql
(that is a period in front of 'dump').
collections.sql is a script file to create a new database with:
Code:
cd /var/local
sqlite3 my.db </mnt/us/collections.sql
similarly with all other *.db files in /var/local
then read them and tell us which ones are related to the other ones.

Those would make a good couple of examples for the runme thread.

See also:
http://www.sqlitetutorial.net/sqlite-dump/

or a runme script to schedule a regular running of a script to backup the database files with cron/at
maybe once a week?

Last edited by knc1; 12-15-2017 at 07:34 AM.
knc1 is offline   Reply With Quote