Hi,
you can activate a Domain with: /usr/local/psa/bin/domain --on domain.xxx
and deactivate the automatic Backup ;-)
/usr/local/psa/bin/pleskbackup domains-name <domain> --split=256M --skip-logs --output-file=/backup/20130526/pleskbackup-<domain>.nl-20130526.bak
/usr/bin/perl /usr/local/psa/admin/bin/plesk_agent_manager domains-name --owner-uid=00000000-0000-0000-0000-000000000000 --owner-type=server --split=268435456 --session-path=/usr/local/psa/PMM/sessions/2013-05-26-120441.675 --output-file=/backup/20130526/pleskbackup-<domain>-20130526.bak <domain>
[3619]: 10:58:02 DEBUG Execute: /usr/local/psa/admin/bin/pmmcli --get-task-status 3621
[3619]: 10:58:03 DEBUG The get task status is executed with errorcode '0'
[3619]: 10:58:03 DEBUG The pmmcli output:<?xml version="1.0" encoding="UTF-8"?>
<response>
<errcode>0</errcode>
<data>
<task-status task-id="3621">
<working>
<dumping total-accounts="0" completed-domains="0" completed-accounts="0" total-domains="1">
</dumping>
</working>
</task-status>
</data>
</response>
Domains [0/1]
1+0 records in
1+0 records out
31457280 bytes (31 MB) copied, 0.203521 s, 155 MB/s
This is happening for me, starting after MU52. The process appears to be hanging during a mysql dump which i see unchanging in ps:
/usr/bin/mysqldump --defaults-extra-file=/tmp/filesGhJTf -h localhost -u admin -P 3306 --quick --quote-names --add-drop-table --default-character-set=utf8 --set-charset XXX-_XXX_wp
If i execute this command from my shell, it runs quickly and correctly.
[23:18:41|INFO: 2642:p.log] Get discovered names
[23:18:41|INFO: 2642:p.log] Search object dirs
[23:18:41|INFO: 2642:p.log] Search object dirs
[23:18:41|INFO: 2642:p.log] Search object dirs
[23:18:41|INFO: 2642:p.log] Search object dirs
[23:18:41|INFO: 2642:p.log] Search object dirs
[23:18:41|INFO: 2642:p.log] '.discovered' directory for 'domain' '7b122095-b3b9-4839-9dfa-804420eb9798' not found
[23:18:41|INFO: 2642:p.log] pmm-ras finished. Exit code: 0
There is no Info, that the migration and transfer Problem has been fixed! Is this also fixed?
Yes, this issue is fixed in MU#53 - http://kb.parallels.com/116173