- Plesk Onyx
How backup rotation works?
To save disk space, it is possible to set up the limit on the number of stored full backup files. When such a limit is reached, the oldest backup file is removed so that a new file can be stored. The limit is related to full backup files only (the number of incremental backups is not limited).
When the server-wide limits are set in Tools & Settings > Backup Manager > Settings, the limits on all subscriptions, customer accounts, and reseller accounts are re-calculated according to the specified value. All newly created customer accounts, reseller accounts, and subscriptions will have the specified limit by default.
Note: Backup will be rotated once the new backup will be created.
CONFIG_TEXT: Customer 1 schedules his backup task to run daily (a full backup), and specifies that backup files should be stored for 10 days.
Customer 2 schedules his backup task to run weekly (a full backup), and specifies that backup files should be stored for 6 weeks.
Customer 3 schedules his backup task to run monthly (a full backup), and specifies that backup files should be stored for 5 months.
When you set up a server-wide limit of, for example, 3 backup files, Plesk automatically adjusts the subscription-level limits:
CONFIG_TEXT: For Customer 1, each backup file will be stored for 3 days.
For Customer 2, each backup file will be stored for 3 weeks.
For Customer 3, each backup file will be stored for 3 months.
Customers will be unable to set up greater values for these limits. However, they can set up lower values.
For the additional details refer our documentation