After upgrading my Plesk install past 8.1.1, I encountered a problem with the builtin backup utility. When attempting to create a new backup (either locally or to an FTP repository), I would almost instantly be handed back the error:
Unable to create backup session: Specified file is not accessible
I googled around and found a couple of results, including a support forum that actually had the answer to my problem burried back on the second page.
For whatever reason, Plesk loses the ability to write to its temporary directory, where all backups are held until they are completed (even for FTP destinations). I was easily able to solve this problem by (as root):
chown -R psaadm:psaadm /var/lib/psa/dumps
Note that the original author of the suggestion I used said to chmod 777 the files, but this proved to be unnecessary. I saw that the parent directory was owned by psaadm, and it just made sense that the dumps directory would need to be as well.
In any case, it worked for me. Hope this helps someone…
thanks, i have a dedicated server from a company called Strato, and have the same problem. But with your help i solve the problem.
You are my hero…
Thank you a lot!
Thank you for your help that worked GREAT!
Thank you very much. I can confirm this fixes 8.3.0 installations.
Dan
Thank You!
Hi,
i need to set chmod 777. the folders already were owned bypsaadm.
But now it works too!
thx
Joe
Excellent. Thanks for the fix.
Not sure I’m liking Plesk.
Thank you very much ! This info was very very useful !
I have the same issue but not after the upgrade. Backup works fine until I actually restore one of previous backup copies. It looks like after restoring domain from backup, Plesk screws up a lot with ownership. I first thought that it’s my server to blame but after reading this post I experimented a bit and figured out that that’s ownership issue. When I look at permissions they are fine, same as before the back ud. But ownership is completely messed up.
Thanks very much!:D
Thx bro ! this was the first post i read and i worked right away !! thx for the support
Thx!! This solved my probs too. For me it just works with set chmod 777, after the chown command.
Thanks for your help.
It worked for me on Plesk 8.4.0
Thank you so much. You made my day. Just wonderful.
Cheers.
thank you!
from Tokyo,Japan
You rock man!!!!!!!
THANKS SO MUCH LIFESAVER. It certainly helped me
yeah, same problem with new installed 8.6 and restored backups. But setting correct owner was the hit! Thx a lot
same problem with new installed 8.6 and restored backups…
chmod 777 don’t work… your fix work!
thank you!
Thank you! In my case, the permissions were wrong and the ownership was wrong. Set to 755, and ran the recursive chown and everything is good again!
Hiii !!!!
Thanks very much !!!!!!
You are the kind of people that makes this live better !!!!!
Thanks, I had that problem when I update at Fedora 7 and Ples 8.6.0, but now it’s all ok.
Thanks a lot, this solved the problem right away !
thank you from poland!!!
Thank you very much!
thank you so much!!
For my updated 8.6.0 this was the answer. Thank you very much!
1 more THANK YOU
Thanks for posting this and steering me in the right direction!
Note that in my case dumps was already in ownership of psaadm but the files and folders inside were in ownership of root. So the key was changing ownership recursively so that all contents of dumps are also owned by psaadm instead of root.