Description of the backup situation.
When performing a backup on a server with the VestaCP control panel, backups of sites and databases are created. In the process of creating backups, site files and data, as well as databases, are first copied and stored on disk. However, a successful final backup requires additional free disk space.
When creating a backup in VestaCP, approximately twice as much free disk space is required, since during the process of creating a backup, site and database data is copied and saved. A copy of the data takes up additional disk space, in addition to the space already used by the database and site files.
Due to lack of free disk space, MySQL stops working. The reason is that MySQL uses a certain amount of disk space for its work, including storing database data and temporary files. If there is not enough free disk space, MySQL may shut down because it cannot continue processing queries and writing data.
Thus, if there is not enough free space on the disk to store backups, this can lead to difficulties with MySQL and even stop it. Therefore, it is important to ensure that you have enough free disk space to perform a backup on VestaCP in order to avoid such situations and ensure the normal operation of the MySQL database.
When the VestaCP backup fails or the MySQL service stops, here are some recommendations to check:
- Low disk space:
- Check if there is enough free disk space to create a backup:
If there is no free space, you need to clean up old logs, journals, unnecessary backups or temporary files. Logs cannot be deleted, only cleared.
- Try clearing the backup queue with the command:
- Stopping a backup. If the backup does not stop, run the command to force the compression process to end:
killall -9 gzip
- If you need to stop all cron jobs, run the command:
service cron stop
- Make sure the permissions on the /home/backup directory are set correctly. Run the command:
chmod -R 775 /home/backup
- Restarting the VestaCP panel. To restart the VestaCP panel, run the command:
service vesta restart
- Make sure the MySQL root /root/.my.cnf password matches the password specified in the /usr/local/vesta/conf/mysql.conf file.
- Check VestaCP configuration files or CMS config files for errors.
2. Backup error log.
Check the log file /var/log/vesta/backup.log for more information on errors. Be guided by the error codes for performing backups, which may indicate the reason for the unsuccessful operation. Pay attention to the error codes and their comments to determine the possible causes of this situation.
Next, you can already navigate by the error code:
|0||OK||Command completed successfully|
|1||E_ARGS||Not enough arguments|
|2||E_INVALID||Object or argument is invalid|
|3||E_NOTEXIST||Object does not exist|
|4||E_EXISTS||Object already exists|
|5||E_SUSPENDED||Object is suspended|
|6||E_UNSUSPENDED||Object is already suspended|
|7||E_INUSE||The object cannot be deleted because it is being used by another object.|
|8||E_LIMIT||Object cannot be created due to hosting package restrictions|
|10||E_FORBIDEN||The user cannot access the object.|
|12||E_PARSING||Configuration not working|
|13||E_DISK||Not enough disk space to complete the action|
|14||E_LA||Server busy to complete action|
|15||E_CONNECT||Connection failed. Host not available|
|16||E_FTP||FTP server not responding|
|17||E_DB||Database server not responding|
|18||E_RRD||RRDtool failed to update database|
|19||E_UPDATE||Update operation failed.|
|20||E_RESTART||Service restart failed|
These guidelines will help you solve some common errors when backing up the VestaCP server control panel.