Recent content by Dmitry Y.

Plesk gives the list of files to pack to the /bin/tar. It's the error from the tar. Such sort of warnings could be ignored. I don't know how to workaround such behavior, exept using of file exclude list, which currently doesn't supported

Here the link you could follow https://cscontact.plesk.com/form/32/?Product=Plesk

You should contact support to get it fixed

Returning back to the original problem with perl warnings. I've tried to run your command ang got the same result. But these warnings are not critical and backup works well. It hangs because of waiting of input on STDIN. If you run it manually from console just press Ctrl+D to identify end of...

Yep, pleskbackup does not support backup copying between repositories. But why you intrested in dump rotation? It is an option for scheduled backup. Are you having own cron task for backup creation, instead of build-in backup scheduling feature?

By using private utility you have a risk of behavior changing in future releases. What do you mean about 2 ways to make a backup? pleskbackup and plesk_agent_manager? Actually pleskbackup is a wrapper, which prepared input for the plesk_agent_manager. It is a historical division, when...

Thanks for feedback! I would like to comment your suggestions: a) Currently there are no way to exclude web content files or folders from backup. But you can wait it in the next release. Now just ignore such kind of messages in the log. b) As I understood you want to be able to create several...

Simply run /usr/local/psa/admin/bin/plesk_agent_manager server -c But it would be better if you will use /usr/local/psa/bin/pleskbackup utility instead of plesk_agent_manager, as plesk_agent_manager is non-public utility

Thank you for report. I've created bug ticket

It would be better to contact support. You can use tasks.db file deletion as a workaround until support solve the issue.

As I can see it tries to get backup process status, but can't obtain its pid. Lets try to rename /usr/local/psa/PMM/tasks/tasks.db to tasks.db.bak It will be recreated on Backup Manager page reload.

Try to remove all *.pyc files from /usr/local/psa/admin/share/pmmcli/

Yes, you are right.

Actually Plesk backup password protection is not about protecting of end-user sensitive data, but it is a protection of the Plesk itself to avoid leak of the panel's passwords. You can vote for backup encryption feature on UserVoice service, which is tracked by Plesk project managers...

To find the answer you have to check your backup logs for any errors or warnings. Possibly with debug logging turned on. As soon as you have execution status = success, I guess it can be some fault action after backup. If there are no errors in the log files you may simply ignore such letters