• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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