Magento 2 Database Backup Button for the Admin
SKU: DBBACKUPBUTTON1
- one click in the admin starts the database dump in the background
- compressed file outside the web root, download only with permission
- retention by count or days, protected backups
- log with user, time, size and status
Einmaliger Kauf · inkl. 12 Monate Updates · zzgl. MwSt.
Magento 2 Database Backup: one click instead of SSH
The Magento 2 Database Backup from Mironsoft adds a button to the admin that creates a database dump in the background. The file is compressed, stored outside the public web directory and can only be downloaded with the matching permission. Old backups are removed according to your retention rule, and every action is written to a log. The interface uses the standard admin components, so the storefront gets no extra code. That turns the Magento 2 Database Backup into a routine that even staff without server access can run before a risky change.
Backup by button
One click in the admin starts the database dump. The job runs in the background and the page stays usable.
Compressed and verified
The file is stored as gzip with a checksum, so damaged backups are easy to spot.
Download by permission
A dedicated ACL resource controls who may create, download or delete. Downloads use a one-time link.
Retention
Keep the last N backups or everything from the last X days. A cron job deletes older files.
Exclude tables
Log, report and session tables can be skipped. That saves space and time in large shops.
Activity log
An admin grid shows who started which backup, how large it is and whether it succeeded.
Why merchants want a Magento 2 Database Backup in the admin
Before an update, a price import or a larger catalog change, everyone should have a fresh backup. In practice this often fails because only one person can reach the server over SSH. Searches such as how to create a Magento 2 backup or back up the Magento 2 database show how common the question is. Magento itself ships no backup button in the admin.
The Magento 2 Database Backup removes that hurdle: whoever has the permission clicks, waits for the done message and downloads the file. It does not replace your hosting provider backup strategy, it adds a quick snapshot before risky work.
Start and monitor a Magento 2 Database Backup in the admin
The admin shows a Database Backup entry under System. One click creates a job that a cron run or the message queue processes. The status moves from waiting through running to done or failed. If something goes wrong, the message from the database tool is written to the log, so you see the cause without searching on the server. While a job is active, no second one is started.
- Live status: waiting, running, done, failed
- No double start while a job is active
- Error message in the log, not just a failed flag
Download backups: permissions, one-time link and storage location
Files are stored in the var directory, explicitly not under pub, and cannot be reached through the web server. Downloads go through an admin controller that checks the ACL resource and creates a link that expires after a short time. Permissions can be granted separately: creating for the shop manager, downloading only for the technical team, deleting only for the administrator. The storage path can also point to a mounted drive.
- Separate ACL rights for create, download and delete
- One-time link with a short lifetime
- Storage path outside the web root, freely selectable
Control retention and disk space for the Magento 2 Database Backup
You choose between count and age: for example the last five backups or everything from the last 14 days. A backup can be marked as protected and then survives the rule, for instance the state before a major upgrade. Before it starts, the module checks the free space at the target and aborts with a clear message instead of leaving a half-written file.
- Retention by count or by days
- Mark single backups as protected
- Free disk space checked before the start
Exclude tables and run backups on a schedule
Large log and report tables inflate every Magento 2 Database Backup although they are rarely needed for a restore. In the configuration you list tables that are saved as structure only. Optionally the module also runs a nightly job. Restoring is deliberately not done in the admin but with the usual database tools, so one click can never overwrite the live data.
- Back up tables as structure only
- Optional nightly run through cron
- No restore function in the admin, by design
Where a Magento 2 Database Backup helps in daily work
Four typical situations in which a fresh backup matters.
Before an update
Right before an upgrade or module installation, the developer or agency runs the Magento 2 Database Backup and marks the file as protected.
Before bulk changes
Anyone changing prices, categories or attributes through an import has a fallback point within seconds.
Small teams without an admin
The shop manager triggers the backup personally and does not have to wait for the server administrator.
Handover to the technical team
The team downloads the compressed file and loads it into a staging environment.
Magento 2 Database Backup: manual over SSH versus with the module
What changes in the daily routine.
| Topic | Without module | With Mironsoft DB Backup Button |
|---|---|---|
| Starting | Only with SSH access and a command line | Button in the admin, controlled by permissions |
| Download | Over SFTP, often with credentials sent by mail | One-time link through the admin |
| Cleanup | Old dumps stay on the disk | Retention rule with cron cleanup |
| Traceability | No overview | Log with user, time and size |
| Disk space | Noticed only when the drive is full | Pre-check and size display |
How we set up the Magento 2 Database Backup for you
The process after you order.
Consultation
You tell us the storage location, retention and the roles that may create and download backups.
Installation
We install the Magento 2 Database Backup, check the database tool, cron and file permissions and create the storage path outside the web root.
Exclusion list
Together we decide which tables are saved as structure only.
Test
We run the Magento 2 Database Backup, download it and load it into a separate database as a test.
Handover
Your team gets a short introduction to the log, protection flag and cleanup.
Difference to server backups, admin permissions and database cleanup
A server or hosting backup protects the whole system on a fixed schedule. The Magento 2 Database Backup delivers a quick snapshot exactly when you need it. It does not replace the hosting backup. Role management is covered by other Mironsoft modules, and so is cleaning up old data; this module only creates backups and only removes its own.
All modules can be combined. The interface uses the standard admin components, and the Hyvä storefront stays untouched.
No download, personal setup instead
DB Backup Button is not listed here as a ready-made download file for self-installation. The purchase is a service commission: we get in touch after the purchase, install the module in your shop and agree on storage location, retention and permissions together with you.
Frequently asked questions
Everything about backups, downloads, permissions and how the purchase works.
How can I create a database backup in the Magento 2 admin?
Where is the backup stored?
Who may download backups?
How long are backups kept?
Can I restore a backup directly in the admin?
How large is the file in a big shop?
Does a backup block the running shop?
Does the Magento 2 Database Backup work with Hyvä?
Does the module replace my hosting backup?
Can I download and install the module myself?
Recently Viewed Products
Magento 2 Database Backup – Mironsoft