• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Question about backups

zachanthonyuk

New Pleskian
Hello,

My Plesk server has suddenly started to run out of disk space, and after a bit of searching the main culprit seems to be a backup_user-data_{date}.tgz file from a particularly large domain + subdomains. I'm trying to figure out why this file exists.

Plesk has only one scheduled backup, which is server-wide, and which is stored externally via FTP. Backup manager only shows these external backups in its list.

I did mistakenly start a local backup at around the time stamp of this large .tgz file, but I thought I had cancelled it (by deleting it in the list of backups in Backup Manager). I'm wondering if this (and other backup_user-data files) are somehow related to this local backup - maybe it wasn't cancelled properly? If this is the case is there a safe way to find and clean all these backup files, to get some disk space back? Or to get Backup Manager to see them again, so I can clean them via that?

Or are these normal and should be left alone? If so, what generated them? Will they be replaced or added to?

Thanks in advance.
 
Back
Top