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:
The backup logs shows the following errors:
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
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