- Plesk Onyx 17.5 for Linux
Restoring website takes too long and finishes with a warning.
/var/log/plesk/PMM/restore/<date-time>/deployer.loglog file contains the following error messages:
CONFIG_TEXT: FailedDatabaseContentDeployment[e20c5c09-6e28-4326-8173-0a7da40c0574]: Errors occurred during deployment of database content. Not all content may be restored. Resolve the errors if required or try to restore the content manually from the archive: databases/wordpress_v_1[sqldump]: backup.tgz [./repository_unpacker.cpp:750]
TransportError[ece3c34a-e815-40ed-85df-33d0d32c4b44]: Transport error: File 'databases/database_name/backup_1709030607_1709150607.tgz' not found [./transport.cpp:495]
CONFIG_TEXT: /usr/lib/plesk-9.0/sw-tar: httpdocs/~: Cannot mkdir: No space left on device
/usr/lib/plesk-9.0/sw-tar: httpdocs/~/~: Cannot mkdir: No such file or directory * There was a previous backup restoration attempt that has finished with the following error in the corresponding /var/log/plesk/PMM/restore/<date>-<time>/deployer.log:
CONFIG_TEXT: ERR [panel] DB query failed: SQLSTATE[HY000]: General error: 1030 Got error 28 from storage engine, query was: DESCRIBE `locales`:
There are backups with duplicate timestamps in Backup Manager: one stored on an FTP server, one stored locally:
The backup downloaded from FTP server is corrupted due to insufficient disk space on the Plesk server.
1. Login to Plesk as admin
2. Remove the local backup duplicates from Backup Manager (be careful not to remove the backups on the FTP server).
3. Provide double as much free disk space on the server as the full backup size (initial+incremental). Such space is required because Plesk downloads the archive from FTP to a local repository and unpacks it before restoring. Below is an example of the required disk space calculation:
CONFIG_TEXT: 15.0 GB incremental + 42.2 GB initial backup = 57.2 GB is to be downloaded to the server during the restoration task.
57.2 GB * 2 = 114.4, as the data from the backup files will be unpacked.