Introduction:
The article descibes Basic information on the MariaDB.
The custo diagnostic server can work with MariaDB databases. (https://mariadb.org/). MariaDB is an open-source MySQL database.
Installation
The installation runs through the setup, a service is installed "diagserverdb". This service then runs mysqld.exe server, which provides the data.
Default setting: c:\Program Files\custo diagnostic server\mariadb\bin\mysqld.exe "--defaults-file=c:\diagserverdata\Default call:mariadb\my.ini" "diagserverdb"
Services
The database then runs on the localhost of the server under port 3306.
By default, the MariaDB server data is located in the same directory as the CST files in the mariaDB
Konfiguration-File
It's here: c:\diagserverdata\mariadb\my.ini
And describes the location, data directories and port of the database
Tools
Basic tool to look into the database: HeidiSQL https://www.heidisql.com/
Extended tool (fee required, except express version): dbForge Sutdio for MySQL https://www.devart.com/de/dbforge/mysql/studio/
Logfiles
The main logfile is *.err and is located in c:\diagserverdata\mariadb
The name consists of the workstation name and the file extension .err
https://mariadb.com/kb/en/library/overview-of-mariadb-logs/
Issues during installation / Reinstallation
If you reinstall the custo diagnostic server for update purposes (but you should actually use the update function of the setup), errors may occur under certain circumstances.
After uninstalling custo diagnostic server you should first check that no "mysql" process is running, this should be checked in the Task Manager. If this is the case, the process should be killed or the computer should be restarted. You should also check that the program directory of the custo diagnostic server is completely removed. Under certain circumstances, a reboot should also be performed for this purpose.
If the error occurs after the new installation that the database can no longer be started, you can correct the error by first uninstalling the custo diagnostic server again as described above. Then you must delete the multi-master.info, all *relay* files and all *.info files in the database directory. Afterwards, you should try a new installation.
Importing the backup
In the Diag data directory there are SQL scripts in the "backup" directory that represent a backup of the entire Diag database in MariaDB. These scripts can be reimported for backup purposes. However, it may be necessary to make a backup before importing the backup itself (see "Making a Backup")
For the following instructions please run a Windows CMD Shell as administrator.
First the diagserver must be shut down:
net stop diagserver
But the diagserverdb service (i.e. MariaDB) must still be running!
Now you can import the backup file with the following command to overwrite the database with the backup. But for this we need the password for the database. The password is located in the custo diagnostic server installation directory in the file conf\diag.properties. This file contains the entry diag.dbPass=[...]. The password is the characters after the =.
We first change to the directory with the backup files and then execute the mysql command located in the installation directory of the custo diagnostic server under mariadb\bin.
cd \diagserverdata\backup "C:\Program Files\custo diagnostic server\mariadb\bin\mysql.exe" -uroot -p<Passwort> diagdb < 2020-01-10.db.backup.sql
This would bring in the backup from 10.1.2020. Please note:
- The password comes after -p but without spaces!
- The user comes after -u without spaces and is always root
- After the password comes the name of the database, which is called diagdb
Afterwards you can restart the custo diagnostic server:
net start diagserver
Create a Backup
You can make a backup at any time (even when the custo diagnostic server is running). To do so, you need the password of the database, as in "Importing the backup". The following command is used for this:
"c:\Program Files\custo diagnostic server\mariadb\bin\mysqldump.exe" -uroot -p<Passwort> -r backup.sql diagdb
This command creates the file backup.sql which contains a backup of the database diagdb.
Automatic Backups
Are created automatically. First one hour after server start, then every 24h.