Best Practices for Plesk and Server Backups

Julian Bonpland Mignaquy

Updated December 10, 2025 14:00

Plesk for Windows kb: how-to Plesk for Linux

Question

What are the recommended best practices for backing up a Plesk server and ensuring both server-level and Plesk-level disaster recovery?

Answer

When planning backups for a Plesk environment, it is important to understand that there are two different layers of backup: the server (VM) backup and the Plesk data backup. Each protects different parts of the system. The most reliable backup strategy combines both.

1. Understand the difference between Server Backups and Plesk Backups

Plesk Backup Manager backs up websites, databases, mail content, DNS zones, subscriptions, customers, and Plesk configuration. It does not back up the operating system, system packages, services, or the full server filesystem.
Server-level (VM) backups or snapshots are performed through the hosting provider (e.g. OVH, AWS, Azure, VMware, Hyper-V). They include the entire machine (OS, configurations, services, and Plesk data) and are required for complete disaster recovery.

2. Recommended Best Practices

A. Weekly Full Server Backup / Snapshot
Create a full image of the server once per week using a dedicated solution such as the Acronis Backup Extension for Plesk or your hosting provider’s built-in backup or snapshot functionality. This allows the entire server to be restored quickly if it becomes unbootable or experiences critical damage.

B. Daily Incremental Server Backups
If supported by your provider, schedule daily incremental VM backups. Incrementals save only changed data, reducing backup time and storage usage.

C. Continue Using Plesk Backups for Granular Recovery
In addition to server-level backups, run regular Plesk backups. These are ideal when you need to restore:

a single domain or website
a mailbox
a database
a subscription or customer

This avoids the need to restore the entire server for small issues.

E. Store Backups in Separate Locations

Keep at least one backup inside the same datacenter for fast recovery.
For Plesk backups, consider using remote storage: S3-compatible storage, FTP , Amazon S3 Backup Storage, Google Drive Backup Storage, DigitalOcean Spaces Storage, Microsoft OneDrive Backup Storage, Dropbox.

F. Automate and Monitor Backups

Schedule both Plesk and server backups so they run automatically.
Regularly verify that backups complete successfully.
Set retention policies appropriate to the business needs.

Summary
A complete backup strategy for Plesk should always include:

Server-level backups (provider snapshots or Acronis) for full disaster recovery
Plesk backups for granular restore of websites, mail, and databases

Using both methods together — especially with a dedicated solution like Acronis Backup Extension — provides the highest level of protection and ensures that you can quickly recover from any issue, whether small or catastrophic.