Restoring Virtual Servers which were running MySql on Virtualmin 7 with Ubuntu 22.04 fails because it insists on using MariaDB

Virtualmin
1
SYSTEM INFORMATION
OS type and version Ubuntu 22.04
Webmin version 2.021
Virtualmin version 7.7
Related packages MySQL vs MariaDB

I am upgrading from Ubuntu 18.04 which is running Virtualmin GPL 7.7, to Ubuntu 22.04 with a clean re-install.
Even if I follow your recommendation of purging MariaDB and installing MySql Server before launching the post install wizard of Virtualmin, I end up with Virtualmin wanting to use MariaDB.
Re-importing the virtual servers which were running under MySql into the MariaDB environment doesn’t work.
Is there some way you might consider giving users a selectable option in the install script where they could choose which DB they wish to use?
Presumably this is a fairly common scenario …
Many thanks!

Update: after some more experimenting, it seems to help if one reboots the machine after purging MariaDB and before first logging into Webmin.
So the sequence from an SSH connection to a machine running Ubuntu 22.04 would be this:

wget http://software.virtualmin.com/gpl/scripts/install.sh

/bin/sh ./install.sh

#remove mariadb
apt purge "mariadb*" -y
apt autoremove -y

apt update
apt upgrade
apt install mysql-server
systemctl start mysql.service

It would still be more user-friendly if the install script could provide an interactive choice for the database to be used.

1 Like
2

Hello,

Coming from someone that had the same fear that a restored database would not work from MySql, I will briefly say something.

The machine I backed up and transferred from was the following:
Operating system Ubuntu Linux 18.04.5
Webmin version 1.955 Usermin version 1.803
Virtualmin version 6.12
MySQL version 5.7.31-0ubuntu0.18.04.1

I transferred it to a new install within the past week with the following (default install of MariaDB):
Operating system - Ubuntu Linux 22.04.2
Webmin version - 2.021
Usermin version - 1.861
Virtualmin version - 7.7
Perl version - 5.034000
Path to Perl - /usr/bin/perl
Python version - 3.10.6
Path to Python - /bin/python3
BIND version - 9.18
Postfix version - 3.6.4
Mail injection command - /usr/lib/sendmail -t
Apache version - 2.4.52
PHP versions - 8.1.2
Logrotate version - 3.19.0
MariaDB version - 10.6.12
ProFTPD version - 1.37
SpamAssassin version - 3.4.6
ClamAV version - 0.103.8

The backup I performed was a backup using Virtualmin’s backup and restore between the old and new server.

I wanted to do this to test exactly what you are seeming to want to stay on MySql for to see if there were any adverse effects.

What was hosted on this was a Joomla 3.10 website and I have not seen any adverse effects on the transfer.

I do hope this helps alleviate some of your fear of switching from MySQL to MariaDB.

I did setup the new server in a “test” environment where I was able to test the effects of this restoration as well without hampering the old production server.

Good Luck

3

Hello, and many thanks for your detailed feedback!
I’m still deliberating which of the three possibilities to use:

  • in-place upgrade from Ubuntu 18.04 to22.04
  • new clean install, forcing Virtualmin 7 to use MySQL instead of MariaDB
  • clean install with MariaDB and re-importing the saved backups…
4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.