Subj : Database documentations and migration
To   : All
From : Vince Coen
Date : Wed Dec 05 2018 07:08 pm

Hello All!

I considering looking at the migration of the internal mbse database 
processing to a RDB system and would
like to use MySQL / Mariadb.


Why you ask?
Well the issue of sharing the DB with other parallel mbse systems running is 
the primary requirement but
the efficiency of it over the internal one is another although not so much - 
at least until DB files get
screwed due to corruption or other.


I have not purchased at great expence a Raspberry Pi 3B+ along with a spare 
HDD sitting on a dock.
Still have to work out how to get it to boot to it as their instructions do 
not work but at least I can
mount it to /home/mbse if nothing else.


How solution is to run often a rsync to the various directories within (but 
not ~/bin) but that may
require a very frequent process that would take up a lot of Lan bandwidth.

The best idea would be to use a common RDB system as I have Mariadb on my 
server, MySQL on a very rairely
used Mac Pro dual xeon quad core system (2008) that I was thinking of selling 
but could possibly just use
it for a MySQL server (Parallel) or do Parallel on the Pi does depend on 
performance a bit.
No I am not assuming the Pi will do a good job so will more than likely stick 
to the server as it is
always up 24/7.  The problem is if it gets sick :(  Hence the reason for using 
the Pi as a back up
system.



Has anyone done any examinations of the mbse code base to see what programs 
use what DBs, what the
structure of each is and where in the code of each program the DB processing 
is done or does it use a
modular approach to call specific routines in one module?


Any advanced help would be very welcome,

Even more so with my eyesight :(


Vince

--- Mageia Linux v6 X64/Mbse v1.0.7.11/GoldED+/LNX 1.1.501-b20150715
 * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

.