Plesk backups
Backup for Plesk, by ALMC
Plesk backups: protect and restore your website
An update goes wrong, a file is deleted or a server needs replacing. Protect your Plesk websites with encrypted backups and recovery points for each site.
We help you connect Plesk and decide what to protect, how often to back it up and how long to keep it. Already a customer

Built for agencies, businesses and teams managing multiple websites in Plesk.
Block-level deduplication
More backups, better use of your storage plan
Keeping ten backups does not mean storing your website ten times. Data blocks already in your repository are reused across backups, rather than stored again for every recovery point.
Alongside incremental backups, the system detects repeated content at block level, not just file level. When part of a file changes, new blocks are saved and existing ones are reused, helping you make better use of your storage allowance.
Choose the date you need and recover that backup without manually assembling a chain of incremental archives.
Request a quoteExample: three backups of a 100 GB website
The website stays at 100 GB; subsequent backups replace 5 GB and 3 GB with new blocks.
| Recovery point | New content |
|---|---|
| First backup | 100 GB |
| Second backup | + 5 GB |
| Third backup | + 3 GB |
| Unique content retained | 108 GB |
108 GB of unique content versus 300 GB in three separate full backups, before compression.
Illustrative example, not a savings guarantee or billing figure. Actual usage also includes metadata, indexes and encryption overhead; it varies with compression, changes and retention. Deduplication takes place within the same repository.
Plesk backups for failures, updates and migrations
Explore three everyday situations and how Backup can help.
Restore your website from an earlier backup
If an update or a change takes your website offline, review the available backups and choose the recovery point you need.
- Backup history for each subscription.
- Restore the files and databases included in the backup.
- Confirm the scope before overwriting.
Recovery requires a valid backup from before the change.
Create a backup before updating your website
Request a manual backup from Plesk and check the result. Start work once you have confirmed the backup is complete.
- Request a backup from the subscription itself.
- Track the operation in Plesk and ALMC.
- Schedule backups so you do not have to rely on remembering.
The server must be linked and have a repository and policy assigned.
Migrate your Plesk websites to another server
Connect the destination Plesk server and prepare to recover selected subscriptions from available backups, even if the previous server is no longer running.
- Choose the sites you want to move.
- Check compatibility with the destination.
- View results and warnings for each site.
Warnings stay visible: your team reviews outstanding issues before considering the migration complete.
Website backups, managed in one place
Work conveniently from Plesk, with a clear overview of all your servers in ALMC.
Request a quoteFile and database backups
Files and databases for the sites covered by your policy, using the actual paths of each domain and subdomain.
Scheduled and manual backups
Combine scheduled backups with manual copies before an update, a handover or an important change.
Efficient backup storage
Keep different versions without saving the same data over and over. You decide how long to retain them.
Backup monitoring and alerts
Review failures, storage issues and detected backup or SQL files. Make informed decisions about exclusions.
Backup history for each subscription
See what was done, when it finished and which recovery points are available for each subscription.
Support for your website backups
ALMC helps you size your storage, connect your server and review your recovery needs.

Plesk server migration from your backups
Replacing a server or recovering from a failure should not mean starting every site from scratch. Backup brings together your backups and the available information to help you make the move.
- Recover the subscriptions you choose, without necessarily restoring the entire server.
- Keep the files, databases and hosting configuration captured in the backup.
- Review a report for each site, including compatibility warnings that need attention.
Application validation and switching traffic are handled separately. The DNS zone is not restored.
Set up your Plesk website backups
You do not need to understand the backup engine. You need to know what you are protecting and how to recover it.
Link Plesk to the backup service
We install the required components and link your server to ALMC using the extension code.
Define your website backup plan
Together, we define the sites, storage, backup frequency and retention period.
Check your backup and recovery
We review the first backup and agree on a recovery test so you understand the actual scope of your protection.
Questions about Plesk backups and website recovery
No. Backup is an ALMC extension and service with its own protection and recovery system. Backups created in the native Plesk manager do not automatically appear here.
In the repository assigned to your server, with the data encrypted. Backups reuse content already stored to avoid duplication. During setup, we agree on capacity, location and retention.
The files and databases covered by your policy, plus the hosting information captured in the backup. Coverage depends on the configuration and supported capabilities. The DNS zone is not restored, and email or other services not specified are not automatically included.
Yes. Once the server is linked and protection is configured, open Backup within the subscription. You can request a backup and access scheduling, history and recovery according to your user permissions. Management remains centralised in ALMC.
Detected ZIP or SQL files are not deleted automatically: they are reviewed before exclusions are decided. During migration, PHP and database compatibility warnings are displayed. If an import fails, the report flags it and other sites can continue; your team reviews outstanding issues.
Tell us how many servers and sites you manage, how much data they hold and how long you want to keep your backups. We will propose a scope and quote tailored to your environment before activating the service.
Get Plesk backups and protect your websites
Tell us how many websites you manage and how much storage you need. We will propose protection that fits and help you connect your server and schedule your backups.
