Hi guys, Just wanted to report this with the error code line below: Some errors still stop a backup despite "Action on error" set to "Continue with other features and servers": E.g. When a user is deleted during backup:
I have an scheduled daily virtualmin backup that backs-up to local files and a remote ssh server.
Today, during the backup, a WHMCS API automatically deleted a user and its main domain and subdomains.
The corresponding backup failed with following error:
Virtual server green111.com cannot be backed up as it has been deleted!
<tt>setquota: user theunion does not exist.
</tt> at ../web-lib-funcs.pl line 1397.
Deleting backups from local file /home/backups1/mu-%Y-%m-%d older than 3 days ..
Deleting directory /home/backups1/mu-2015-10-23, which is 3 days old ..
.. deleted 24.93 GB.
.. deleted 1 old backups, and skipped 4 that were not old enough
Deleting backups from /mnt/data1/backups/mu/mu-%Y-%m-%d on SSH server backups.xxxx.com older than 5 days ..
Deleting file /mnt/data1/backups/mu/mu-2015-10-21 via SSH, which is 5 days old ..
.. deleted 12 kB.
.. deleted 1 old backups, and skipped 6 that were not old enough
In the local and remote folders, some backups are missing today, as well as the Virtualmin backup file: virtualmin.tar.gz (and .info and .dom).
And in Backup Logs, "Final size" is "0 bytes", despite the virtual servers before the failing ones having been backuped.
As a result, because of one missing domain and a second domain where the user got deleted during backup, the whole server backup is incomplete today.
Also, minor, there is this strange "" formatting tag in that error.
Comments
Submitted by JamieCameron on Tue, 10/27/2015 - 23:14 Comment #1
Yes, this is a bug - but it will be fixed in the 5.0 release of Virtualmin.
Submitted by beat on Wed, 10/28/2015 - 02:32 Comment #2
Thanks Jamie! You're on top of things! :-)
Submitted by Issues on Wed, 11/11/2015 - 01:34 Comment #3
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Wed, 11/11/2015 - 01:34 Comment #4
Automatically closed -- issue fixed for 2 weeks with no activity.