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

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Plesk 11.5: Daily backup fails after update

meap_it

New Pleskian
Hello everyone,

we just updated our plesk panel on a debian 6 server from version 11.0 to 11.5 a few days ago and since that day our daily backup fails every night.

The backup script is executed by the cron daemon.

This is the backup script:
Code:
#!/bin/bash

BASEDIR=/srv/backup
DATE=`date +"%Y%m%d_%H%M%S"`
DIR="$BASEDIR/$DATE"

echo "deleting old backups..."
rm -rf $BASEDIR/2*

echo "creating backup-dir..."
mkdir $DIR

echo "back to root..."
cd /

echo "writing plesk backup..."

/opt/psa/bin/pleskbackup server --output-file=$DIR/plesk_vollbackup

echo "moving mysql-dump..."
mv $BASEDIR/mysql* $DIR/

echo "changing ACL..."
chmod -R 644 $DIR/*

echo "cleaning up..."
rm -rf $BASEDIR/clients
rm -rf $BASEDIR/.discovered

echo "backup done!"

The backup logs shows the following errors:
Code:
[2013-09-12 02:19:02.433| 6778] INFO: pmm-ras finished. Exit code: 0
[18552]: 00:19:02 ERROR ebd29f11-bf22-450f-8ecb-eacdf54c745a The dump have been invalidated by check-dump operation
[18552]: 00:19:02 ERROR 209d0c01-9c6a-4754-8797-87fed46da0a8 Runtime error: The check dump failed with code '1'. The dump can contain invalid data! at /opt/psa/admin/bin/plesk_agent_manager line 1230.
 at /opt/psa/admin/bin/plesk_agent_manager line 1230
	main::checkDump('Storage::FileStorage=HASH(0x34e9a88)', '/srv/backup', 'HASH(0x33f4048)') called at /opt/psa/admin/bin/plesk_agent_manager line 687
	main::perform('verbose', 0, 'owner-type', 'server', 'split-size', undef, 'session-path', '/opt/psa/PMM/sessions/2013-09-12-010013.472', 'all', ...) called at /opt/psa/admin/bin/plesk_agent_manager line 1311
	main::__ANON__() called at /usr/share/perl5/Error.pm line 416
	eval {...} called at /usr/share/perl5/Error.pm line 408
	Error::subs::try('CODE(0x34dec70)', 'HASH(0x34defa0)') called at /opt/psa/admin/bin/plesk_agent_manager line 1319
	main::main() called at /opt/psa/admin/bin/plesk_agent_manager line 1323.
: 
 at /opt/psa/PMM/agents/shared/Logging.pm line 100
	Logging::error('Runtime error: The check dump failed with code \'1\'. The dum...', 'fatal') called at /opt/psa/admin/bin/plesk_agent_manager line 1317
	main::__ANON__('Error::Simple=HASH(0x3a69360)', 'SCALAR(0x294c1a0)') called at /usr/share/perl5/Error.pm line 340
	eval {...} called at /usr/share/perl5/Error.pm line 330
	Error::subs::run_clauses('HASH(0x34defa0)', 'The check dump failed with code \'1\'. The dump can contain i...', undef, 'ARRAY(0x294dcd0)') called at /usr/share/perl5/Error.pm line 427
	Error::subs::try('CODE(0x34dec70)', 'HASH(0x34defa0)') called at /opt/psa/admin/bin/plesk_agent_manager line 1319
	main::main() called at /opt/psa/admin/bin/plesk_agent_manager line 1323

We already opened a support case (#1727673) but we want to know if anyone else in the community has experinced this kind of failure?! Maybe someone got a quick solution or answer?

Thanks for any feedback
Florian
 
Same problem

Hi,
I use plesk 11 since one year without any problem. We did the 11.5 update, two weeks ago and, since then, we have the same error in our web console. So I don't have any completed backup since the update. Did you receive a reply from Parallels team ?

Thanks a lot

Yannick
 
Similar/Same problem

Was that solved? Because we have just experienced the same problem...
We use Plesk 11.5.30 #25 . Last update was Nov 29, but suddendly Dec 4 we got error: "Unable to create dump" on daily backups...

In backup logs we got:
Code:
[24214]: 02:19:56 ERROR f869f3e7-bfeb-4ed7-8d44-010732eb3fd6 Unable to create dump: 
 at /usr/local/psa/PMM/agents/shared/Logging.pm line 100
	Logging::error('Unable to create dump', 'fatal') called at /usr/local/psa/admin/bin/plesk_agent_manager line 678
	main::__ANON__('Error::Simple=HASH(0x5e36d80)', 'SCALAR(0x26dd2f8)') called at /usr/share/perl5/Error.pm line 339
	eval {...} called at /usr/share/perl5/Error.pm line 329
	Error::subs::run_clauses('HASH(0x3978e68)', 'Unable to write to output file: Input/output error at /usr/lo...', undef, 'ARRAY(0x3978c70)') called at /usr/share/perl5/Error.pm line 426
	Error::subs::try('CODE(0x39790a8)', 'HASH(0x3978e68)') called at /usr/local/psa/admin/bin/plesk_agent_manager line 680
	main::perform('verbose', 0, 'owner-type', 'server', 'split-size', undef, 'session-path', '/usr/local/psa/PMM/sessions/2013-12-03-234303.470', 'profile-name', ...) called at /usr/local/psa/admin/bin/plesk_agent_manager line 1311
	main::__ANON__() called at /usr/share/perl5/Error.pm line 415
	eval {...} called at /usr/share/perl5/Error.pm line 407
	Error::subs::try('CODE(0x3280650)', 'HASH(0x3280980)') called at /usr/local/psa/admin/bin/plesk_agent_manager line 1319
	main::main() called at /usr/local/psa/admin/bin/plesk_agent_manager line 1323

Another problem with that is that in server Backup Manager is written "No backups.", when it should be. In backup storage there is backups, but Backup Manager does not show them at all.
 
Ok, for me problem was solved. It was not backup error, the disk was set to read-only in the middle of the backup, that`s why I got this error.
 
Back
Top