• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Backup process failed - Error code 255

davidakus

New Pleskian
I have had this problem for about a month now. Scheduled backups have not been running. Manual backups also fail. Both give this message:

Error: The backup process failed: pmm utility '/usr/bin/perl /usr/local/psa/admin/bin/plesk_agent_manager server --get-size --incremental --session-path=/usr/local/psa/PMM/sessions/2019-09-11-153438.659' raised an exception. Error code is: 255 See pmmcli.log to find out detailed information on this

I have looked through pmmcli.log and cannot find any further information to help me. I can provide the log if needed, but it is quite large (and being new here, am unsure of the best way to add it to this post).

Server information:
OS: ‪CentOS 6.10 (Final)‬
Product: Plesk Onyx Version 17.8.11 Update #67, last updated on Sept 11, 2019 03:22 PM

Thanks!
 
I have looked through pmmcli.log and cannot find any further information to help me. I can provide the log if needed, but it is quite large (and being new here, am unsure of the best way to add it to this post).
In this case, I'd suggest you contact Plesk Support Team. They will check and fix the issue directly on your server.
 
Back
Top