MedBackupPrestaShop module 1.6 to 9.x
Your whole store, backed up and kept safe.
MedBackup backs up every file of your store into a single archive, with no size limit, and sends it to Dropbox, Amazon S3 or FTP. If the server interrupts the backup, it picks up where it left off, even on the largest sites.
- 0
- size limit: beyond 4 GB and 65,535 files
- 2×
- faster: images are not recompressed
- 5
- destinations: Dropbox, Amazon S3, FTP, FTPS, SFTP
01 - The problem
A backup that fails silently
On a large store, a standard backup runs into the server's limits. And nobody notices until they need it.
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 archive stays incomplete.
The ZIP format hits a ceiling
Beyond 4 GB or 65,535 files, the standard ZIP format can no longer cope. A store with a large image catalog quickly exceeds both thresholds.
The copy stays on the same disk
An archive kept on the store's server disappears with it in case of failure, hacking or cancellation of the hosting plan.
02 - How it works
A backup that goes all the way
On a dedicated server as well as on the most restricted shared hosting.
Core engine
Step by step, with resume
The backup moves forward in short steps whose duration adapts automatically to your server. Its progress is saved: if interrupted, it restarts from the exact file.
ZIP64
No size limit
The archive is written on the fly, in ZIP64 format. Images and already compressed files are stored as is: the backup runs about twice as fast.
Off the server
Sent to safety
Dropbox, Amazon S3 and compatibles, FTP, FTPS or SFTP. On Dropbox and S3, the upload is sent in chunks and resumes after an interruption.
03 - Comparison
Web host, standard backup module, MedBackup
Three ways to back up a store's files.
| Web host backup | Standard backup module | MedBackup | |
|---|---|---|---|
| Backup right before a risky operation | Depends on the plan | Yes | Yes, in one click |
| Store larger than 4 GB | Yes | Often blocked | Yes, ZIP64 |
| Resume after a server interruption | Not applicable | No, starts over | Yes, from the exact file |
| Copy off the server | Often | Depends on the module | Dropbox, S3, FTP, SFTP |
| Cache and thumbnails excluded | No | Rarely | Yes, by default |
| Database in the same archive | Separate | Depends on the module | Yes, with our database module |
| Protected and checked archives | Yes | Folder often exposed | Random folder, checked daily |
| Run by an employee without full access | No | No | Yes, settings reserved to the super admin |
Keep your web host's backups. They cover the whole server. MedBackup covers what they do not: an immediate copy, under your control, sent where you decide.
For a complete copy, pair it with our database backup module: its latest dump is added to every archive.
04 - Video
The module in action
A real backup run from the back office: the database, the files then the upload to Dropbox, each phase with its own color, then the settings. Silent video.
05 - For merchants
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 color: database, files, upload. The final summary tells you whether the archive arrived safely.
- Smart exclusions
- Cache, thumbnails, WebP and AVIF copies from image conversion modules, and the folders you tick in the store's file tree.
- Local and remote archives
- Two sortable lists: archives on the server and on Dropbox, to download or delete in one click. The oldest ones are removed automatically.
- Database included
- With our database module, its latest dump joins every archive. With an active license, a fresh dump is run just before the files.
- Cron or command line
- Over SSH, the backup has no time limit. Without SSH access, a cron URL chains the steps through redirects.
- Logs and FAQ
- Every backup, upload and download is logged. A built-in FAQ answers common questions without leaving the module.
06 - Security
An archive that contains the whole store
It is protected accordingly.
Access
- Settings and archive downloads reserved to super admins
- Other employees can start a backup and follow it
- Restrictions enforced by the server, not just hidden
- Email link to the back office: without login, it gives access to nothing
Archives
- Randomly named folder, protected on Apache
- Daily check, rule provided for nginx
- Dropbox access limited to the module's own folder
- No library loaded from a CDN, no native table modified
07 - Technical
Technical specifications
Broad compatibility, designed for large stores.
- PrestaShop
- 1.6 to 9.x, all major versions
- PHP
- 5.6 to 8.4, 64-bit for archives over 2 GB
- Archive format
- Standard ZIP64, opened by every system
- Destinations
- Dropbox, Amazon S3 and compatibles, FTP, FTPS, SFTP
- Launch
- Button, command-line cron or cron URL
- Languages
- 17
- Multistore
- Yes, the whole installation is backed up
- Zip extension
- Not required, the module writes its own archives
The day everything breaks, your store is back up.
A first backup in one click, a cron task for the rest, a copy kept safe off the server.