HI, am using the Virtualmin built-in Backup System for all virtual servers/domains…
Am using a load and lot of databases, esp. with Wordpress. I read that many backup system often have issues with (mysql/mariadb-)database backup & restoration.
What are your experiences, hints and suggestion to make backups a secure way for my 36 domains??
Considering the latest patches to MySQL library, it should handle MySQL/MariaDB difference and most importantly version difference quite well, and way better than before (will be included to Virtualmin 6.13). You could update mentioned file, restart Webmin and give your backups a try.
It’s recommended to make sure that MySQL root password is set and working. The easiest way to do so, is to re-run Post-install Wizard and re-setup MySQL root password there (it will not be required after Virtualmin 6.13 release).
As I understand it, on my server there are X domains/virtual servers, which I can backup with the aforementioned system.
But there is also a folder root etc, with all the “meta” stuff, openvpn, root files etc… this wouldn’t be covered by any virtual server …
All the root server installations, BIND, OpenVPN, apache - not sure etc, the backup system itself, all server settings IP etc etc … how do I backup this??
I’ve found the webmin database backup system to be quite lacking. I typically end up using PHP My Admin to do the DB dump and need to automate it. Right now just doing it as part of my daily admin of my instance.
It seems when I use WBN/VMN do to it, the DB’s aren’t complete. I would imagine I’m doing something incorrectly (most likely), so for the time being I just export them all via phpMyAdmin and know that I have 100% of all the DB’s.
I recently tested restoring some Virtualmin backups just to make sure they work. I created a couple of virtual machines on my desktop (one CentOS and one Ubuntu), installed webmin and virtualmin the usual way and then restored some virtualmin backups (of individual sites) and everything looks fine, including mail accounts.
What did NOT work well was restoring webmin configuration files (using Webmin > Backup Configuration Files > Restore) at the server level. That’s not surprising for various reasons but the lesson to learn is that this type of backup shouldn’t be restored unless you really have to. They’re fine for recovering from an accidental misconfiguration but not for migrating from one server to another or restoring to a new server.
I use automysqlbackup (in addition to Virtualmin backups) to backup database contents to the server. It works well and on Ubuntu is installed simply using “sudo apt install automysqlbackup”, no configuration needed.
The advantage is that these backups (which are in plain SQL text format, rotated daily weekly and monthly) can then be backed up along with website source files to cheap external storage such as a NAS or OneDrive.