Improve the logic on how the WordPress Toolkit creates instance backup
WordPress Toolkit during backup process creates full plain copies of the database and files in the webspace before the compression. If Hard quota is enabled it is needed to have twice more allowed space otherwise it fails
Plesk Tech Support
shared this idea
-
Plesk Tech Support
commented
During the WP backup process there is an intermediate plain SQL database and WP files created in the temporary folder:
ls -l /var/www/vhosts/example.com/.wp-toolkit/backups/351
total 20972
drwxr-xr-x 3 sysuser psacln 4096 Apr 28 16:16 files
-rw-r--r-- 1 sysuser psacln 21468967 Apr 28 16:16 sqldump.sql
Since this DB and Files folder belong to the system user of the Domain, such files consume the hard quota of the disk.
So the following situation can happen:
- The hard quota is 4GB
- The website size is 2GB
The customer thinks that there is enough space to create a WP zip backup
During the WP backup process additional 2GB of temporary files are created, which is causes the "zip I/O error: Disk quota exceeded", and the backup process fails on the zip creation step since it requires more than 4GB of space
Please make the backup process more straightforward (for example the temporary files are no longer belong to the system user and therefore do not count as hard quota)
Or, as an alternative, make a notification before the backup that will prevent such backups with the explanation that more space is needed and why