PrestaShop module 1.6 to 9.x
Your whole shop, backed up, kept safe and restorable.
MedBackup backs up the database and every file of your shop, sends them off the server to one or several storages, checks every copy and restores the database in one click, without taking the shop offline.
- 2
- in one backup: the database and the files
- 0
- size limit: over 4 GB and 65,535 files
- 5
- storage types, several at once: Dropbox, S3, FTP, FTPS, SFTP
01 - The problem
A backup that fails silently
A backup is only worth something if it is complete, kept safe and restorable. It is often on the day of the failure that you find out something was missing.
The server stops it before the end
Most hosting plans kill a script after 30 to 300 seconds. A backup run in one go stops halfway, and the copy stays incomplete.
Database and files are kept apart
Two tools, two sets of settings, two schedules: the database and the files are not from the same moment, and one of them ends up forgotten.
Restoring is the riskiest step
Re-importing a database through phpMyAdmin breaks on large tables and leaves the shop half empty. And a copy left on the server disappears with it.
02 - How it works
A complete backup that goes all the way
On a dedicated server as well as on the most restricted shared hosting.
Backup plans
Database, files or both
Each plan picks its content, its frequency, the number of copies kept and its storages. The database every 4 hours, the full backup every night: ready as soon as the module is installed.
Step by step, with resume
No size limit
Database through mysqldump or a step-by-step PHP engine, files in a ZIP64 archive. If the server interrupts it, the backup restarts from the exact point.
Off the server
Checked and restorable
Sent to several storages at once, read back after writing, checked to the byte on Dropbox. The database is restored in one click, the shop stays online.
03 - Comparison
Web host, standard backup module, MedBackup
Three ways to back up and restore a shop.
| Web host backup | Standard backup module | MedBackup | |
|---|---|---|---|
| Database and files | Yes, the whole server | Often one or the other | Yes, in the same backup |
| Backup right before a risky operation | Depends on the plan | Yes | Yes, database snapshot in a few seconds |
| Plans with their own content and frequency | No | A single task | Yes, from every hour to every month |
| Shop larger than 4 GB | Yes | Often blocked | Yes, ZIP64 |
| Resume after a server interruption | Not applicable | No, starts over | Yes, from the exact point |
| Copy off the server | Often | Depends on the module | Several storages at once: Dropbox, S3, FTP, SFTP |
| Check of every copy | Not visible | Rarely | Yes, read back and checked to the byte on Dropbox |
| Database restore | On request, often the whole server | Manual import | In one click, shop online, safety copy first |
| Alert when a backup is missing | No | Rarely | Yes, in the module and by webhook |
| Run by an employee without opening everything to them | No | No | Yes, settings and restore reserved to the super administrator |
Keep your web host's backups. They cover the whole server. MedBackup covers what they do not: the immediate copy, under your control, sent where you decide and restorable from the back office.
Already using our Database backup module? MedBackup imports its settings and its backups, which stay restorable.
04 - Video
The module in video
The backup plans, a manual "Database and files" backup followed live then sent to Dropbox, the list of backups, a database restore preceded by its safety copy, then the diagnostics. Video without sound.
05 - Merchant side
Everything is managed from the back office
You see what is backed up, where, and what happened.
- Live progress
- A window follows the backup phase by phase, each with its own colour: database, files, upload. Close the page, it resumes when you come back.
- One-click restore
- Restore button on a database backup, local or on Dropbox. Each table is rebuilt aside then swapped in one go: never an empty table.
- Snapshot before an intervention
- Before an update or a theme change, the database is copied in a few seconds and kept until you delete it.
- Smart exclusions
- Cache, thumbnails, WebP and AVIF copies, folders ticked in the folder tree with their weight, tables picked from the list with their size.
- Diagnostics and alerts
- Server limits, database, backup folder, storages and plans: each point is OK, Limited or a Problem, with advice. A late plan is flagged.
- Logs and webhook
- Every backup, upload, download, restore and deletion is logged. A webhook notifies Slack, Discord or any URL, or only when something fails.
06 - Security
A backup that holds the whole shop
It is protected accordingly.
Access
- Settings, downloads, deletions and restores reserved to super administrators
- Other employees can launch a backup and view the lists, with secrets masked
- Restore confirmed by typing the database name
- Email link to the back office: without logging in, it gives access to nothing
Backups
- Randomly named folder, protected on Apache, exposure checked, rule provided for nginx
- Every copy read back after writing, checked to the byte on Dropbox
- Dropbox access limited to the module's own folder, no secret stored
- No library loaded from a CDN, no native table modified, no override
07 - Technical
Technical specifications
Broad compatibility, designed for large shops.
- PrestaShop
- 1.6 to 9.x, all major versions
- PHP
- 5.6 to 8.5, 64-bit for archives over 2 GB
- Database
- mysqldump or step-by-step PHP engine, as .sql.gz, .sql or .zip
- Files
- Standard ZIP64 archive, no PHP zip extension needed
- Storages
- Dropbox, Amazon S3 and compatibles, FTP, FTPS, SFTP, several at once
- Launch
- Button, command-line cron, curl or webcron URL, one line per plan
- Languages
- 6
- Multistore
- Yes, the whole installation is backed up
The day everything breaks, your shop is back.
Database and files backed up according to your plans, a checked copy off the server, a database restorable in one click.