Donaldson R F
Servers & Hosting (Plesk, CloudPanel, Linux)
Plesk Backup Setup & Troubleshooting
Get Plesk's backup manager actually working and storing backups somewhere safe off the server.
The Problem
Plesk has backup tools built in, but a misconfigured schedule, a full local disk, or a broken remote storage connection means you can go months thinking you're covered when you're not.
About this problem
Plesk's backup manager works, but a schedule that was never actually enabled, a local disk that quietly filled up, or remote storage credentials that expired are all silent failure modes — the backup button looks the same whether it's working or not. Months can pass before anyone notices there's nothing usable to restore from.
This typically comes up after a near-miss (a bad update, an accidental deletion) makes someone check their backups for the first time and find there's nothing there.
What's Included
- Configuring backup schedules for the domains that need them
- Connecting remote storage (FTP, S3-compatible, or similar)
- Running a real backup and a real restore test
- Confirming you'll actually be notified if a backup fails
What's NOT Included
- Ongoing storage costs for remote backup space
- Disaster recovery planning beyond Plesk's own backup manager
- Recovering from a specific existing data loss (separate recovery service)
How It Works
- Check whether a backup schedule currently exists and is actually running, not just configured.
- Set up or correct the backup schedule for the domains that need it.
- Connect and test remote storage (FTP, S3-compatible, or similar) so backups don't sit only on the same server.
- Run a real backup, then a real restore into a test location to confirm the files are actually usable.
- Confirm failure notifications are enabled so a broken backup gets flagged, not discovered months later.
In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.
Frequently Asked Questions
- Does Plesk back up automatically by default?
- No — a backup schedule has to be explicitly configured per domain or server; a fresh Plesk install has no backups running until one is set up.
- Where should Plesk backups be stored?
- Off the same server where possible — FTP or S3-compatible remote storage, since a backup stored only locally is lost along with everything else if that server fails.
- How do I know if my Plesk backups are actually working?
- Checking the backup history shows success/failure per run, but the only real confirmation is periodically restoring a backup and verifying the result — which is part of this service.
- Can Plesk backups fail silently?
- Yes — a full local disk, expired remote storage credentials, or a misconfigured schedule can all stop backups without an obvious alert unless notifications are specifically set up.
- How often should website backups run?
- Daily is standard for an active site; less frequent for a mostly static one — the right frequency depends on how much change (and potential loss) you can tolerate between backups.
- What's the difference between a full and incremental Plesk backup?
- A full backup captures everything each time; incremental only captures changes since the last backup, which is faster and smaller but depends on the full backup it's based on still being intact.