Never mind the following error:
It means that such permission does not supported in Plesk 12.5 and will be ignored on backup
Really usefull is the following error:
It means some critical error occured on domain content archiving.
I asked you is your server is a part of Windows domain managed...
No, you can't do it with Plesk extension. Try add your suggestion on Uservoice (http://plesk.uservoice.com/forums/184549-general). It is a real way to get it done in future release, as PMs track this resource to include some most wanted ideas to the next release feature set
You quite right. Currently there are no special protection of user content in the backup. Plesk protects only its sensitive data, web content archived without any encryption. So end-user should care about backup security, if those backups are outside Plesk environment (Personal FTP storage or...
It is not clear where do you see the error? Migration consist of several stages: conflicts detection and resolution, backup and restore. You should check log, as mentioned above. Additionally check also %plesk_dir%\admin\logs\php_error.log
Now check also %plesk_dir%\admin\logs\php_error.log
I suppose you should see there some errors for backup_restore_helper utility called with parameter --backup-subscription or --backup-site
Seems like XML parser got non-XML data. Could you enable debugging (http://kb.odin.com/en/120101) and repeat backup again?
It helps to get more information. Backup logs can be found at %plesk_dir%\PMM\logs\backup*
Never seen such behaviour. Can't imagine how is it possible.
You should check latest folder content in the /usr/local/psa/PMM/msessions to find out more information about possible issues. Pay attention to files objects_list, objects_list_raw, migration.log and also check...
Try to replace the files /usr/local/psa/PMM/plesk.xsd and /usr/local/psa/PMM/restore-specification.xsd with these from attach. The same changes should be installed with MU#40, have you installed it?
Never seen so many errors of such kind...
When you see "This element is not expected" it usualy means that element itself is correct, but placed wrong. According to XSD tags on this level of XML placed in wrong order.
E.g.
backup_info_1509160104-formatted.xml:141: element scheduled-tasks...
There are an issue in Plesk for Unix version (PPP-11017), that DUMP_TMP_D actually does not used for exporting dumps to FTP. Instead it uses /usr/local/psa/PMM/tmp
You can mount some storage to this path as workaround
Sorry, I supposed you have a backup exported with Plesk tools and "plesk_webserver.sg_info_1509010300.xml" actually is a tar. Now I see it is not.
So you have a copy of your /var/lib/psa/dumps from the source server and "plesk_webserver.sg_info_1509010300.xml" is a root XML file from this dump...
The easiest way is to import your dump first and then restore from UI
To import the dump call:
/usr/local/psa/admin/bin/pmm-ras --import-file-as-dump --dump-file-specification=/root/plesk_webserver.sg_info_1509010300.xml --dump-storage=/var/lib/psa/dumps/ --type=server...
No. there are no special setting for timeout control. If you enable debug in panel.ini backup log will contain FTP connection RAW commands. It may help to find possible problems.
Which version of Plesk do you use?
/usr/bin/getcontrolpaneluserspackages is not a part of Plesk. May be you should start investigations from the CloudLinux side? Try to address yor question to support
You need to enable debug mode (http://kb.odin.com/en/120101)
Then repeat the backup to FTP and see logs at /usr/local/psa/PMM/session/<dir_with_latest_timestamp>/psadump.log
grep by phrase "Curl output" to see possible FTP problems