Schedule Plesk Server Backups with Deliberate Retention

Plesk’s server administrator can schedule backups through Tools & Settings > Backup Manager. This is separate from a customer’s or reseller’s permitted backup scope. The available schedule and storage features depend on the installed version, license and administrator configuration.

Configure the approved server task

1. Use authorized administrator access and open Backup Manager > Schedule.
2. Select Activate this backup task for the intended schedule. Activation enables scheduling; it is not the same as starting an immediate manual backup.
3. Choose the supported frequency, run time and full/incremental configuration. Read the installed interface’s retention units carefully.
4. Select configuration, mail, user files and database scope deliberately; choose the approved destination and error-notification address.
5. Save, inspect the configuration, then verify an actual scheduled artifact and any remote upload.

Read retention according to the release

Current server-administrator documentation describes the maximum number of full backup files, including scheduled and manual copies, while other role/version pages describe time-based retention. Do not copy the old “leave blank to keep forever” advice into an unfamiliar form. Confirm what rotation will delete and preserve a known recovery point independently before changing it.

Keep all required full/incremental components together and let supported rotation manage chains. A missing or corrupt base can prevent recovery. Database treatment may differ from incremental web/mail files; do not assume a generic changed-files copy describes every component.

Balance consistency and availability

Capacity, temporary working space, backup overlap and remote storage limits matter. Domain suspension can interrupt service and needs coordination; it is not a checkbox to enable blindly. Use supported protected storage and retain required passwords/keys outside the server.

Verify recovery, not just scheduling

Review task status, warnings, destination artifacts and failure notifications. Test a representative restore in a contained compatible environment with live integrations disabled. Do not infer success from a saved schedule or a single compressed-file integrity check.

This is a configurable Plesk procedure, not an InterServer automatic backup or retention guarantee. Confirm the actual policy for your service separately.

References: Plesk server-administrator scheduling and rotation; component and incremental-backup scope.

Reviewed October 15, 2026. Documentation review; no live schedule, retention, domain suspension or restore was changed or executed.