• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

Hungry Backup

R

redpaint

Guest
Hi All,

We've just upgraded to 9.2 from 8.3 and we had 4PSA's Total and Client backup running on 8.3.

After upgrading we're finding that most, if not all, of our client's domains are having their resources eaten up by backups. The backups appear as XML files under the client's Backup Manager tool. Once the resources (disk space) has gone their domains are suspended and they become angry and call us.

We've gone through all the accounts and enabled resource over-use to stop clients from calling but the core issue remains:

Despite no client/domain backup schedule being active, backups are still taking place and consuming disk space. How and where can we stop this from happening?

We have disabled the ClientBackup cronjob so this shouldn't be causing the problem.

Thanks in advance!
 
You can exclude domain backups from disk space calculation:

Home > Settings > Settings of Server Statistics

Uncheck "domain backup files".
 
Hi,

Thanks for the reply, that might keep clients from being auto suspended, however it doesn't stop the disk space being eaten up. Clearly this 'feature' is a major oversight/bug if we are expected to remove backups from the disk space calculation and then manually remove them once we find we have run out of disk space. Does anyone at Parallels actually read these forums??
 
Back
Top