Virtualmin backup does not created sql files (anymore)

SYSTEM INFORMATION
OS type and version Ubuntu 22.04.3 LTS
Webmin version 2.105
Virtualmin version 7.8.2

I am using the Backup and Restore feature and I followed the steps in the guide exactly. Previously it was working fine when I had the schedule set to once per week, but when I changed to once per day, the .sql files still only backup once per week. I implemented the same thing on a second clean VM, and in that case the .sql backup files do not get created at all. The terminal output seems fine, including a “Dumping MariaDB database …” line for each server. Any help would be appreciated, thanks.

Hello,

Do you have scheduled backups configured to perform incremental type of backups?

Hi. The “Backup level” is set to “Full (all files)” and the “Features to backup” to “Backup all features”. If I understand the “Incremental” option correctly, then only files that changed will be backed up. In my case I have almost the opposite effect – on the first VM I only see the sql files from the previous Sunday and on the second VM no sql files at all. This is the first week that I noticed the issue.

Indeed, that’s correct, but this doesn’t apply to databases. Databases are always subjected to complete backups.

Are the databases still associated with virtual server? It can be checked in Edit Databases page.

Yes, the database appears under Edit Databases. I can also download the .sql backup manually from phpMyAdmin, and if I place this in the folder next to the .tar.gz file from where I restore, it works correctly.

How does the file structure appear for an extracted incremental backup file?

Do you mean which folders are present in the .tar.gz file? And is this different for incremental and full backup? I see folders such as awstats, bin, cgi-bin, etc. Is there something specific that I should look for? Should there be any hints about the .sql database in the .tar.gz?

Yes, database backups should be inside of the hidden .backup directory.

Okay I see the .backup folder now. Maybe this is the crucial question: How many files should the Virtualmin Backup create for each server? I previously had 4 (.tar.gz, .tar.gz.dom, .tar.gz.info and .sql), and now have only 3 (same except the .sql). I thought this was a problem, but if all the SQL data is located in the .tar.gz then perhaps not? (Or does Virtualmin never create a .sql next to the .tar.gz? Maybe that is a remnant from some other backup solution.)

No, all files should be inside .tar.gz file.

Thanks for all the help @Ilia . I had a separate cron job that was interfering with my backups.

Can you tell more about what was happening and how exactly it was interfering?

I can’t remember when / how I set up this other cron job, but it was also making a copy of the MySQL databases to the same folder that I chose for the Virtualmin backups, so I thought the .sql files that appeared next to the .tar.gz was also created by Virtualmin. When I changed the frequency from weekly to daily, I did not understand why the .sql files still only appeared weekly, but it makes sense now. I simply deleted the other cron job and will check that I can still restore the MySQL databases from the .tar.gz alone, but I am sure it will work the same as for everyone else.

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