• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question restore backup not owner

SacAutos

Regular Pleskian
Server operating system version
AlmaLinux release 8.10
Plesk version and microupdate number
Plesk Obsidian 18.0.68 Update #2
I have a situation where I need to restore a backup to look for some lost files. The person who owned the website died last July. I have a backup in cloud storage that I can't restore because the restoration tool says that I'm not the backup owner. The owner's account had been previously deleted from the server. I have recreated it using the same name (I thought) but the restore won't work from either their customer account nor from admin. The container file is 15GB so it's not easy to throw around. Ideas?
 
Follow up on this issue. I wasn't able to restore the backup due to ownership. Since it was above the 2GB file limit, I wasn't able to upload it for restoration either. However, I was able to download it locally and extract the XML file with the backup contents. Using that, I was able to determine that the file(s) that I was looking to find wasn't present. So I have to move on.

However, this experience has opened up what feels like a flaw in the backup/restore system. I understand the purpose of security but making it so difficult to restore a backup container is counter-productive, particularly when I was logged in as admin and have complete access to the cloud storage. This needs to be revisited.
 
Back
Top