• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Backup finishes with "Dump has content errors", no details given

Bitpalast

Plesk addicted!
Plesk Guru
Plesk Onyx 17.5, #25, CentOS 7.2

backup log:
Code:
...
[2017-05-11 02:04:15.400| 7639] INFO: Repository '/var/lib/psa/dumps': Validate incremental backup backup_info_1705060124_1705110124.xml
[2017-05-11 02:04:15.400| 7639] INFO: Find incremental backups in '' for prefix 'backup' and base version 1705060124
[2017-05-11 02:04:15.401| 7639] INFO: Repository '/var/lib/psa/dumps': Get info from .discovered/backup_info_1705060124_1705110124/dumpresult_
[2017-05-11 02:04:15.402| 7639] INFO: pmm-ras finished. Exit code: 0
[25752]: 2017-05-11 02:04:15.670 ERROR 2191df25-71fa-4dee-81b1-e93aee3d973b The dump has content errors!
[25752]: 2017-05-11 02:04:15.671 ERROR 31a92e46-00d7-487d-8445-cef0298077ea Runtime error: The dump has content errors! at /usr/local/psa/admin/bin/plesk_agent_manager line 1263.
:
 at /usr/local/psa/PMM/agents/shared/Logging.pm line 116.
        Logging::error('Runtime error: The dump has content errors! at /usr/local/psa...', 'fatal') called at /usr/local/psa/admin/bin/plesk_agent_manager line 1382
        main::__ANON__('Error::Simple=HASH(0x11611d0)', 'SCALAR(0x183bdf0)') called at /usr/local/psa/PMM/agents/shared/Error.pm line 330
        eval {...} called at /usr/local/psa/PMM/agents/shared/Error.pm line 321
        Error::subs::run_clauses('HASH(0x2848b68)', 'The dump has content errors! at /usr/local/psa/admin/bin/ples...', undef, 'ARRAY(0x1847180)') called at /usr/local/psa/PMM/agents/shared/Error.pm line 417
        Error::subs::try('CODE(0x1157a68)', 'HASH(0x2848b68)') called at /usr/local/psa/admin/bin/plesk_agent_manager line 1384
        main::main() called at /usr/local/psa/admin/bin/plesk_agent_manager line 1388

[2017-05-11 02:04:16.443|27511] INFO: pmm-ras finished. Exit code: 0

+ mail sent to admin: "... Runtime error: The dump has content errors! at /usr/local/psa/admin/bin/plesk_agent_manager line 1263.; The dump has content errors!"

pmmcli.log:
Code:
...
[2017-05-11 01:24:18.572|25725] INFO: Outgoing packet:
<?xml version="1.0" ?><response>
    <errcode>0</errcode>
    <data>
        <task-id>468</task-id>
    </data>
</response>

No specific other errors visible in the logs, just the ending as shown above.
 
It's hard to say what's wrong there. You need to look above in the backup log, most likely there will be more errors or warnings. That that you see - result of that in xml there is a link to archive which is not present for some reasons.
 
Thank you both for your support!

A manual full backup followed by a manual incremental backup both worked. A test restore of the full backup to another machine first did not work, but that is a different issue. On further attempts, the test restore did work, too. So, yes, probably in this case it was a temporary issue.
 
Back
Top