If you serve numerous websites, you may want to configure the backup process so that it does not consume much server resources.

To configure server-wide backup settings:

  1. Go to Tools & Settings > Backup Manager (under “Tools & Resources”) > Settings.

  2. (Optional) In the corresponding field, specify the maximum number of full backups files (including both scheduled and manual backups) that can be stored in any type of storage.

    For details, see “Backup Rotation”.

  3. In the corresponding field, specify the maximum number of simultaneously running scheduled backup processes. The default value is 10.

  4. To make the backup processes release resources to other server processes, “Run all backup processes with low priority” is selected by default.

    You can choose to run only scheduled backups with low priority by selecting the corresponding checkbox.

    注解: Both options increase backup time. Other server tasks will not work slower during backing up.

  5. Set the desired compression level from the “Compression level” menu (“Fast” is used by default). Choosing a slower option reduces the size of backup files, but leads to higher CPU usage and longer backup times, while choosing a faster option leads to the opposite result (more disk space usage, less CPU usage, faster backups). This setting affects all backups made on the Plesk server.

  6. To prevent backing up processes from consuming all available disk space on the server, “Start the backup only if your server has the sufficient amount of free disk space” is selected by default.

    This option significantly increases backup time because Plesk additionally calculates the size of the future backup.

    If you know the approximate size of the future backup and do not want Plesk to waste time and resources on calculating it, clear the “Start the backup only if your server has the sufficient amount of free disk space” checkbox. Instead, in “Start the backup only if your server has the specified amount of free disk space”, specify the approximate size of the future backup in megabytes.

    注解: Plesk for Windows 不会直接计算对象大小但是会从数据库提取。因为 Plesk 数据库的对象大小一天只能被更新一次,计算的整体备份大小会因其真实值而不同。

  7. Select whether to allow setting up FTP backup storage on the local Plesk server.

    Users can configure their FTP storage to be located on the same Plesk server where their subscriptions are hosted. If they do so, the amount of used disk space will double upon creation of each backup. This can cause the server to eventually run out of free disk space. To prevent this, we recommend that you do not select the “Allow setting up FTP backup storage on the local server” checkbox.

  8. Choose whether to save backups in the server storage if the upload to remote storage fails by selecting the corresponding checkbox.

    注解: Backing up to the Plesk server storage is possible only for users with the “Backup and restoration of subscription data using the server storage” or “Backup and restoration of account data using the server storage” permissions.

  9. 点击 确定


您可以为在服务器(本地)repository 中存储的所有 Plesk 备份选择保护类型:

  • Plesk’s encryption key. By default, certain sensitive data in a backup (for example, passwords of Plesk accounts) are encrypted with an internal key. The key is unique to each Plesk installation. Encrypting backups with Plesk keys is convenient but has certain limitations. When users restore backups created in other Plesk installations, the data is restored, but the original user passwords are lost, and new passwords are generated instead. In this case, the users will receive password change notifications by email. If you are going to restore a backup on another Plesk installation and want to avoid changing user passwords, use the Specified password option.

    注解: The Plesk internal key encrypts only certain data in a backup but not the whole backup. If you store backups in remote cloud storage, you can enable backup encryption on the cloud storage side.

  • Specified password. You can specify a server-wide password to protect certain data in a backup. This type of protection is preferable and can be recommended in most cases. In particular, this may be useful in case of multiple Plesk installations, or if you store a backup on a mounted drive and use it for restoration if the drive with Plesk crashes. To restore all Plesk data including user passwords, you have to provide the same password that was specified for the backup.

以上描述的安全设置只与存储在服务器(本地) repository 中的备份有关。如果您要在 FTP 服务器上存储备份,请在 FTP 存储设置中配置密码保护。欲知详情,请查看 配置远程存储

注解: 订阅用户在下载备份时指定的密码不要与服务器范围的密码或加密密钥相冲突。对于此类备份,会使用用户指定的密码。请查看 上传和下载备份文件


默认安装了`云存储扩展extension <https://www.plesk.com/extensions/category/clouds/>`__后,您的客户和代理商还可以将其用于存储器手动备份。若要管理客户和代理商允许使用哪个云存储,请购买 Backup to Cloud Pro 功能。

一旦购买了此功能,则能够在以下情况时于 “权限” 标签(在 “显示更多可用权限”)上允许或禁止客户或代理商使用已安装的云存储服务:

  • 添加新的或编辑现有的服务方案和附加方案。
  • 自定义订阅。

image cloud permissions



注解: “使用远程存储备份和恢复订阅数据”权限优先于在云存储中存储备份的权限。如果未选择”使用远程存储备份和恢复订阅数据”,即使选择了相应的云权限,客户和代理商也无法在云存储中存储备份。

Backup Rotation

To save disk space, you can set up a server-wide limit on the number of stored full backups in Tools & Settings > Backup Manager (under “Tools & Resources”) > Settings. When the limit is reached, Plesk irrevocably deletes the oldest backup files to free up space for new ones. We call this process backup rotation.

注解: The limit only affects full backups. The number of incremental backups is not limited.

注解: The limit affects the Plesk server local storage and any configured remote storage.

image 78606

Backup rotation differentiates between manual and scheduled backups. If you have both manual and scheduled full backups whose number exceeds the limit, backup rotation deletes the oldest full backups in the following way:

  1. Keeps the latest manual backup.
  2. Keeps X-1 number of the latest scheduled backups, where X is the server-wide limit on the number of stored full backups.
  3. Deletes all other full backups.

For example, you have three manual backups and three scheduled backups. You set the server-wide limit on the number of stored full backups to three. After backup rotation, Plesk will keep the following full backups: the latest manual backup and the two latest scheduled ones.

Subscriptions, customers, and resellers have their own limits on the number of stored full backups in “Scheduled Backup Settings”. Setting up the server-wide limit changes the corresponding limits for new and existing subscriptions, customers, and resellers to match the server-wide limit value. It will be impossible to set the limits for subscriptions, customers, and resellers higher than the server-wide limit (see the screenshot below).

image 78607

For example, a reseller has “Maximum number of full backup files to store” set to four. After you set the server-wide limit to two, the reseller’s limit will be automatically set to two to match the server-wide limit. The reseller will not be able to change their limit to the value higher than two.