• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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