🖳 Works with Plesk 🧩 No Panel Extension 📍 Off-Server Target 🔐 Optional AES-256 🖳 Works with Plesk 🧩 No Panel Extension 📍 Off-Server Target 🔐 Optional AES-256
Plesk Backup

Back Up the Sites on Your Plesk Server
No Panel Extension, Straight to an External Target

Plesk's own backup protects server configuration, but by default it sits on the same server. Yedekalma backs up your sites' files, MySQL databases and mailboxes and sends them directly to your own cloud — so even if the server is lost, your backups are not.

🎁 Start Free See Pricing

No credit card required · free trial until the end of the year

Complementary Protection

What You Need Alongside a Plesk Backup

These are not competitors: one protects the machine, the other protects the data.

📍

A copy elsewhere

If the server is lost entirely, the backup on it is lost too. An independent copy is essential.

🔐

Optional encryption

When enabled, the archive is encrypted with AES-256 on your server and goes to your storage encrypted; the passphrase is known only to you and we cannot open it.

✉️

Mailboxes

IMAP mailboxes are a separate component and can be written back into the mailbox when needed.

⚡

Incremental transfer

Optional: only changed files, tables and new messages are transferred, so each run stays light.

🗂

Per-site scheduling

Each domain gets its own frequency and target, all visible in one panel.

🦠

Malware scanning

Optional file and database scanning runs on your server during backup (detection only); emails carrying malicious attachments are left out of the archive.

Setup

Four Steps Using Plesk

1️⃣

Download the zip

Add your domain in the panel and download the PHP Backup Module generated for it.

2️⃣

File manager

Plesk → Files → upload into httpdocs and extract; keep the folder name.

3️⃣

Verify from the panel

Press Verify in the panel; the module connects itself — no token to paste.

4️⃣

Schedule it

Pick frequency and target — scheduling is handled on the Yedekalma side.

Scope

Backed up: files in the document root, MySQL/MariaDB databases and IMAP mailboxes.

Not backed up: Plesk's own configuration (subscription definitions, DNS records, email account definitions, SSL certificates). Keep using Plesk's native backup for server-level configuration — together the two give you full coverage.

FAQ

Plesk Backup — Frequently Asked Questions

A Plesk backup includes server configuration and is valuable to a server administrator, but by default it is stored on the same server and needs extra configuration to be sent elsewhere. Yedekalma focuses on application data — files, databases and email — and writes it to your own cloud from the start, so it survives losing the server entirely.
No. Nothing is installed in the Plesk interface. The module goes into your document root as an independent folder and is unaffected by Plesk updates.
Yes, but you install the module once per site; each is managed as a separate domain in the panel. That lets you give each site its own frequency and storage target, and an automatic volume discount applies as your domain count grows.
The module runs on Linux servers with PHP 7.1 or newer (8.1+ recommended). On the database side MySQL and MariaDB are supported; Microsoft SQL Server is not.
No. Scheduling is managed from the Yedekalma panel and triggering comes from our side, so you do not need to create cron entries on your server.

Keep Your Plesk Server Data Off the Server

Configuration stays in Plesk, data goes to your cloud. Free trial until the end of the year.

Create Free Account

See pricing →