| 开发者 | lumenthemesapp |
|---|---|
| 更新时间 | 2026年10月31日 18:12 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp_mail() to the addresses you enter.
LumenThemes Backup Pro
LumenThemes Backup is complete on its own: nothing in this plugin is locked or time-limited. If you also need cloud storage, incremental backups, staging or site migration, those are part of the separate LumenThemes Backup Pro plugin from Lumen Themes.
lumenthemes-backup folder to /wp-content/plugins/ and activate it on the Plugins screen.WP_TEMP_DIR). Encryption uses PHP's OpenSSL extension, or the sodium extension where OpenSSL isn't available; without either, a much slower library that ships with WordPress is used. Scheduled backups use WP-Cron.On your own server, encrypted, in wp-content/uploads/lumenthemes-backup/backups/ (shown under Settings), and every backup file has a random name. The encryption key is stored in your database, not next to the files, so a backup file can't be read even if someone requests it directly. The plugin's folder also contains rules that block web access on Apache and IIS, and backups can only be downloaded through the plugin by administrators.
While a backup or restore runs, its unencrypted files (the database export and the archive before it is encrypted) are kept only in a private folder in the temporary folder WordPress uses, outside your website, and deleted when it finishes. If the server has no usable temporary folder, LumenThemes Backup doesn't run the backup and explains how to fix it: usually by setting WP_TEMP_DIR in wp-config.php to a folder outside your website.
Keep a copy somewhere else as well: download important backups to your computer. Downloads are decrypted, so they are normal files you can open with other tools.
No. Nginx ignores .htaccess files, but backups are encrypted, so a backup file can't be read even if it is requested directly, and unencrypted files are never placed inside your website. If you like, you can also block the folder in your Nginx server block:
location ^~ /wp-content/uploads/lumenthemes-backup/ { deny all; }
Before a restore changes anything, the archive is checked against its seal and a safety backup of your current database is taken. If the database import fails, the safety backup is put back automatically. If the restore finishes but you don't like the result, restore the safety backup from the Backups page. The newest three safety backups are kept.
No. Files in the backup replace the current versions, and files added since the backup are left in place. The database is replaced completely by the one in the backup. Your site address (Settings → General) is kept as it is now.
No. The plugin makes no external connections and has no tracking.
Use .lumen for normal backups. Use .zip when you also want to open the archive with other tools. Use .sql for a plain database export, for example to import with phpMyAdmin.
The scans only read your data. Nothing is removed or compressed until you select it and confirm. Image compression keeps a copy of every original so you can revert it. For extra safety, take a backup before cleaning.
Click Run Audit on the Dashboard. It checks your PHP time and memory limits and suggests what to change. A database-only backup is much faster than a full backup.
Not yet. LumenThemes Backup works on single-site installations and won't activate on a multisite network.
The plugin's database tables, settings, scheduled events and image-optimization records, and the backups stored on this server: they are encrypted with a key that is removed too, so they could not be opened again. Download any backups you want to keep before you delete the plugin; downloaded copies are not encrypted. The original copies of optimized images are kept in wp-content/uploads/lumenthemes-backup/originals/; delete that folder by hand if you no longer need them.