Turkey (Turkish)
Germany (German)
Worldwide (English)
Local preparationDump and temporary file space
Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
The Plesk backup process consists of local dump creation, database export, file packaging, and remote storage transfer. Even if the process writes to remote Google Drive or FTP, the temporary local area, permissions, and PMM logs are critical.
Backup task failed
Not enough free disk space to backup selected objects
Unable to create the remote backup: Transport error
The user specified as a definer does not exist
No space left on devicePlesk can prepare file and database data in the local backup area or temporary directories before sending them to remote storage without sending them to remote storage. Therefore, even if there is free space on the remote target, the /var/lib/psa/dumps partition on the server will not start the process if it is insufficient.
Instead of the general "failed" result on the Backup Manager screen, the relevant task log under /usr/local/psa/PMM/logs should be examined.
If the Google Drive account authorization has expired, the backup list may not be displayed or a transport error may occur. You may need to log in again.
A missing DEFINER user in a MySQL view or trigger can stop the database dump. This error is different from a storage issue.
Successful backup is not just the creation of the archive file. The usability of the backup is not proven until a restore test is performed regularly to a different location.
Disabling the disk control option does not solve the actual space shortage. The backup process can fill up the disk and stop the sites and MariaDB. A capacity plan and remote storage strategy should be implemented together.
Search for the phrase you see in the email, browser, or SSH log. Each card includes meaning, probable cause, and safe initial action.
Meaning: Plesk has not found sufficient space in the local repository for the Plesk backup size estimate.
Possible cause: /var/lib/psa/dumps partition, temporary area or hard disk configuration.
Meaning: The file system was unable to write new data during the process.
Possible cause: Unforeseen growth, tmp space or inode fullness.
Meaning: Plesk remote storage extension failed to send data to target.
Possible cause: Network, API, authorization, token, or provider error.
Meaning: Google Drive connection token is invalid or has expired.
Possible cause: Account permission has been revoked or extension session is broken.
Meaning: FTP/SFTP access or authentication failed.
Possible cause: Incorrect user, passive port, firewall, DNS, or certificate.
Meaning: The MySQL user is being used as DEFINER with view/trigger missing in the database.
Possible cause: User has been deleted or access control has been changed.
Meaning: Some files are unreadable, modified, or lost.
Possible cause: Permission, broken symlink, active write, or malicious file.
Meaning: Archive created but not all items were retrieved completely.
Possible cause: Mail, DB, file or extension subtask failed.
No records matching this expression were found.
Commands are for root access. Collect only status and logs first; Do not change the permanent setting without seeing the reason.
df -hT /var/lib/psa/dumps
df -i /var/lib/psa/dumps
du -xsh /var/lib/psa/dumps/* 2>/dev/null | sort -h | tailThe backup partition shows capacity, inodes, and large archives.
find /usr/local/psa/PMM/logs -type f -mtime -3 -printf '%TY-%Tm-%Td %TH:%TM %p
' 2>/dev/null | sort -r | head -n 20Finds Plesk Backup Manager task log entries from recent days.
plesk bin scheduled-backup --list -allLists scheduled backup tasks on the server.
getent hosts UZAK_HEDEF
nc -vz UZAK_HEDEF 21Checks FTP example DNS and port access; port is changed according to the target type.
plesk db -Ne "SELECT TRIGGER_SCHEMA,TRIGGER_NAME,DEFINER FROM information_schema.TRIGGERS;" 2>/dev/nullProvides an example in the context of Plesk DB access; customer DB permissions and security should be carefully considered.
pleskbackup domains-name example.com -output-file=/var/lib/psa/dumps/eka-test.tar -vCreates a detailed CLI test backup for one domain; sufficient free space must be verified.
ps -ef | grep -E '[p]leskbackup|[p]mmcli|[b]ackupmng'
iostat -xz 1 3Indicates stuck task and disk IO intensity.
First, determine the task log and space requirements; then verify the source item, remote storage, and availability separately.
Open the PMM log corresponding to the date and task ID in the Backup Manager notification.
Leave enough space for dumps and temporary files even if remote backup is enabled.
df -hT /var/lib/psa/dumps && df -i /var/lib/psa/dumpsMySQL definer, if the target storage is changed when a file or mailbox error occurs.
Checks DNS, port, API permission, token, and target quota for FTP/S3/Google Drive.
First, test with a single domain or configuration-only to determine if the issue is related to the size or the tool.
Restore new backup to different test environment; monitor task result and aging backup policy.
If the extension account is Unknown or unauthorized, exit and re-authorize with the correct Drive account.
Plesk can prepare archives and temporary parts locally; /var/lib/psa/dumps and PMM tmp directory are checked.
The relevant DB trigger/view definer, unreadable files, and domain quota are checked.
ps, IO, PMM log, remote network speed and large single files are checked; the running process is not killed blindly.
Archive integrity, Plesk version compatibility, password, and complete download from remote storage are verified.
Plesk can prepare archives and temporary parts locally before sending them to a remote target.
Remote Storage Settings should be removed and reauthorized with the correct account from the Remote Storage Settings section.
Some data may be missing. The warning details should be resolved and a restore test should be performed.
Disk and time can be reduced; however, a regular full backup and restore chain plan is still required.
Backup Manager and retention policy should be preferred. Manual deletion can affect metadata and chains.
Encrypted backups may not be restorable. The key and password should be safely stored separately.
The existence of the archive is less important than successful restore and application test on a different test server.
By analyzing cPanel, WHM, CloudLinux, LiteSpeed, MariaDB, Exim and security layers together, we fix the root cause of the failure instead of just removing the service.