A scheduled Plesk backup should reflect how much data loss and recovery time your website can tolerate. Configure scope, destination, retention and failure reporting together. A schedule that runs regularly but stores incomplete or unreadable archives is not a dependable recovery plan.
IN THIS ARTICLE
What you need before you begin
Confirm available backup features and storage allowance. Decide whether the application needs coordinated write suspension or a specialized database backup for consistency. Configure an independent remote destination and keep any backup protection password in approved recovery storage.
01 Schedule Plesk subscription backups and retention
- Open the subscription Backup Manager and its Schedule settings. Activate the intended task.
- Choose a frequency and start time that fit the application change rate and server load. Review the timezone and avoid overlapping heavy maintenance jobs.
- Select content needed for recovery, including relevant files, databases, mail and configuration. Review exclusions so essential data is not omitted.
- Choose full or incremental backups and the full-backup interval offered by your installation. Incremental recovery depends on the required earlier chain, so retain the supporting full backup and increments together.
- Set the destination, retention and monitored error-notification address. Read the retention units carefully because the interface can express full-backup count or a period. Save and inspect the first completed scheduled job.
How do I confirm scheduled backups are recoverable?
Confirm an archive reaches the intended remote destination, the timestamp and scope are correct, and retention behaves as expected. Perform a restore test of a representative object. Monitor job completion and usable recovery age, not just whether the schedule checkbox is enabled.
Troubleshoot unexpected results
For a failed job, preserve the last good backup and investigate storage, credentials, connectivity and temporary-space requirements. Do not delete an entire incremental chain manually to free a small amount of space. If the necessary schedule or destination requires an unavailable feature, choose a supported backup arrangement rather than assuming an extension is included.