• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/

Backup to FTP-Repository Runtime Error in Plesk 11.5.30

netsetter

Basic Pleskian
After the Plesk 11.5.30 upgrade, creating backups to the FTP-Repository is giving following errors in the Plesk Panel:

Error:

Runtime error: Export dump to FTP failed at /usr/local/psa/admin/bin/plesk_agent_manager line 726.
at /usr/local/psa/admin/bin/plesk_agent_manager line 726
main::perform('verbose', 4, 'owner-type', 'server', 'split-size', undef, 'session-path', '/usr/local/psa/PMM/sessions/2013-06-29-125905.894', 'description', ...) called at /usr/local/psa/admin/bin/plesk_agent_manager line 1298
main::__ANON__() called at /usr/local/psa/PMM/agents/shared/Error.pm line 406
eval {...} called at /usr/local/psa/PMM/agents/shared/Error.pm line 398
Error::subs::try('CODE(0x31fe7c0)', 'HASH(0x31feaf0)') called at /usr/local/psa/admin/bin/plesk_agent_manager line 1306
main::main() called at /usr/local/psa/admin/bin/plesk_agent_manager line 1310.

Error:

The dump have been made successfully but can not be imported to FTP due to errors.
The dump 'backup_mydomain.com_info_1306291259.xml' have been leaved at repository '/usr/local/psa/PMM/tmp/backupQSxcW4'. Please export it manually

Error:

Can't upload file '/usr/local/psa/PMM/tmp/backupQSxcW4/backup_mydomain.com_info_1306291259.xml.tar' to ftp. Error code: 1

It's a bug in 11.5.30? Any suggestions?
 
Ensure that the FTP backup settings are present and up to date, also check that there is enough available space on the drive.

I've just had the same issue and it would appear that the drive was full, or not reachable.

If none of these resolve the issue then ticket it to parallels.
 
Ensure that the FTP backup settings are present and up to date, also check that there is enough available space on the drive.

I've just had the same issue and it would appear that the drive was full, or not reachable.

If none of these resolve the issue then ticket it to parallels.
 
Back
Top