Backing up WordPress with Wupz without anything missing from the backup
Wupz 0.0.4 backs up a WordPress site as a ZIP, at the push of a button or on a schedule, optionally to S3 as well. What is in the backup, what the exclusion patterns leave out, what you should check after the update, and how to restore by hand.
A backup plugin for WordPress is installed quickly. One click, and there is a ZIP file with a date in the admin. But you cannot tell from the ZIP whether the site can be restored from it. You usually only find that out when you need it.
Wupz is my own backup plugin for WordPress. It backs up the database and the wp-content folder into a ZIP file, at the push of a button or daily or weekly through WP-Cron, and optionally also uploads the file to an S3 bucket. Whether such a backup is enough in an emergency depends on a few settings and on two files that never end up in the ZIP in the first place. This text refers to version 0.0.4.
Installing
You download wupz.zip from the releases on GitHub and install it under Plugins → Add New → Upload Plugin. It requires WordPress 5.0 or later, PHP 8.1 or later and the PHP extension ZipArchive. After that the admin has a "Wupz" menu item with the button for a manual backup, the settings and a page for the storage.
What ends up in the ZIP
A backup is called, for example, wupz-backup-2026-10-27_09-30-00.zip and contains two things:
database.sqlwith the structure and content of all tables whose name starts with the table prefix of your installation, usuallywp_- the
wp-contentfolder with themes, plugins and uploads
What is not in it: the wp-config.php, the .htaccess in the root directory and the WordPress core. You download the core fresh in an emergency, that is no loss. The wp-config.php, on the other hand, contains the database credentials, the table prefix and the salts. Without it you have to enter everything again when restoring. So put a copy of this file in a safe place yourself and update it when you change something in it.
Tables without the prefix are missing too. If WordPress and another application share a database, Wupz only backs up the WordPress part.
What is left out
Which files from wp-content do not go into the backup is set in two fields under Wupz → Settings.
"Exclude File Patterns" contains one pattern per line. Out of the box these are cache/, tmp/, temp/, *.log, *.tmp and wupz-backups/. A pattern with a trailing slash means a folder of that name, no matter how deep it sits. * and ? are wildcards that do not reach across a slash. *.log therefore matches every file that ends in .log. Wupz always leaves out its own backup folder, even if you delete the line. Otherwise old backups would sit inside the new one.
"Maximum File Size" is given in MB. The default is 100, and everything above that stays out. With 0 there is no limit.
Both apply silently. There is no message about which files were skipped. So go through the list once: if a plugin stores real data in a folder called temp, or if you have a large video in the media library, you take the pattern out or raise the limit.
If you remove the limit, keep an eye on memory. Wupz builds the database dump completely in memory before it writes it, and the download of a local backup reads the whole ZIP file in at once. With a large database or a large archive that can fail at PHP's memory_limit.
Where the backups are stored
Locally the files end up in wp-content/wupz-backups/. On activation Wupz creates an .htaccess there that blocks access from outside. But that only works if the web server reads .htaccess files. Apache does, provided it is allowed, nginx ignores them completely. The file names follow a fixed pattern of date and time.
You check whether the block works with a request from outside. Use the name of a real backup from the list in the admin for that:
curl -I https://deine-seite.de/wp-content/wupz-backups/wupz-backup-2026-10-27_09-30-00.zip
If 200 comes back, anyone can download this backup, database included. Then you block the path in the web server configuration and check again. With 403 nobody gets to the file from outside.
Even when it is blocked properly, one catch remains: a backup on the same server does not help you when exactly that server fails or gets hacked. That is what the upload to S3 is for.
Uploading to S3
Under Wupz → Storage you enter the access key, secret key, bucket and region. With a custom endpoint this also works with S3-compatible providers instead of AWS. After every backup Wupz uploads the ZIP file to the bucket under its file name. If you also tick "Delete Local Backup" there, Wupz deletes the local file as soon as the upload has succeeded. Then the backup only exists in the bucket.
"Maximum Backups to Keep", default 5, applies locally and in the bucket. In the bucket Wupz only counts and deletes files that are named like its own backups, that is wupz-backup-JJJJ-MM-TT_HH-MM-SS.zip. It leaves other files in the same bucket alone. If the listing fails or the list stays incomplete, it deletes nothing at all. I would still set up a separate bucket, or at least credentials that are only allowed to write there. Then the keys in the WordPress database reach no further than the backups.
Schedule and update to 0.0.4
How often an automatic backup runs is set under Wupz → Settings at "Backup Schedule": "Daily", "Weekly" or "Disabled". After saving, the next backup runs one interval later and then continues at that interval. "Disabled" removes the scheduled run.
If you update from an older version to 0.0.4, look at this setting right away. The saved value now really applies. If you saved the settings in the past while it said "Disabled" there, automatic backups now stay off until you choose "Daily" or "Weekly". If you never saved the schedule, you stay on weekly. The first automatic backup after the update comes one interval later. Whether a run is scheduled is shown on the Wupz page in the admin under "Next Scheduled Backup".
Also new is that *.log and *.tmp files are missing by default from 0.0.4 on. If you need them, delete the two lines from the exclusion patterns.
When you find out about errors
If a scheduled backup fails, Wupz sends an email to the WordPress admin address. That is off by default and is switched on in the settings under "Email Notifications". No message is sent for successful backups.
One gap remains because of WP-Cron itself. Scheduled tasks only run when someone visits the site. On a site with few visitors the weekly backup therefore runs later than expected, and no error email arrives, because nothing has failed. So look at the date under "Last Backup" on the Wupz page in the admin now and then. If you have access to the server, you can switch off WP-Cron with define('DISABLE_WP_CRON', true); in the wp-config.php and have wp-cron.php called by a real cron job instead.
Restoring
Wupz has no restore function. You do it by hand:
- Download the ZIP and unpack it.
- Install WordPress fresh, or keep the existing core files, and put your saved
wp-config.phpin place. - Import
database.sqlinto the database, for example through phpMyAdmin or with WP-CLI usingwp db import database.sql. The dump containsDROP TABLE IF EXISTSfor every table. Existing tables with the same name are therefore replaced. - Copy the
wp-contentfolder from the ZIP back.
Try that once on a test environment before you rely on a backup. Only then do you know whether everything the site needs is in it.
What it is enough for
Wupz is meant for small WordPress sites: schedule checked after the update, the exclusion patterns looked at once, the wp-config.php backed up by hand, the restore tried once, and a look at the date of the last backup now and then. On large sites with a lot of media or a large database it runs into the memory limits mentioned above. There, server-level backups are the better choice, for example snapshots at the hosting provider.
Questions and bugs about Wupz belong in the issues on GitHub.
Common questions
- What does Wupz back up, and what is missing from the backup?
- The Wupz ZIP contains the database.sql with all tables whose name starts with the table prefix of your installation, and the wp-content folder with themes, plugins and uploads. Not included are the wp-config.php, the .htaccess in the root directory and the WordPress core. So you make a copy of the wp-config.php yourself.
- How do I restore a Wupz backup?
- Wupz has no restore function, you do it by hand. You unpack the ZIP, put your saved wp-config.php in place, import the database.sql, for example through phpMyAdmin or WP-CLI, and copy the wp-content folder back.
- Why is my automatic Wupz backup not running?
- Since Wupz 0.0.4 the saved schedule really applies: if you saved the settings with "Disabled" in the past, automatic backups stay off until you choose "Daily" or "Weekly". On top of that, scheduled tasks in WP-Cron only run when someone visits the site. On a site with few visitors the backup therefore runs later than expected.
- Are the Wupz backups reachable from outside?
- Wupz creates an .htaccess in wp-content/wupz-backups/ that blocks access from outside. But that only works if the web server reads .htaccess files, nginx ignores them completely. Check it with a request from outside: with 200 anyone can download the backup, with 403 nobody gets to the file.