Restora
| 开发者 | jbosnakis |
|---|---|
| 更新时间 | 2026年10月31日 19:16 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Full site, or separate files. One zip with everything, or pick the parts (database, plugins, themes, media uploads, WordPress and other files) and get each as its own file, with "Download all" or one by one.
- Made for limited hosting. The backup runs in short slices and continues where it stopped, even in the middle of a large file, so PHP time limits do not break it.
- Restore from the admin. The archive is checked from start to finish first, the database is swapped in one atomic step, and a safety backup of the current site is taken beforehand.
- Bring a lost site back. On a new, empty WordPress, upload a backup from your computer and restore it. Backups of 10 or 20 GB upload in pieces on any host, carry on after a break, and are moved to the new site's address.
- Schedules. Backups of the whole site and of the database every day, every 2 or 3 days, every week, every 2 weeks, every 15 days or every month, at the minute you choose, keeping only the newest ones.
- Standard format. The archive is a normal zip you can open anywhere; the database is plain SQL inside
.restora/. - Closed to the web. Backups live in a randomly named folder and can only be downloaded by an administrator through WordPress.
- It finishes on limited hosting. Restora writes one zip and can pause and resume in the middle of any file, so a short PHP time limit on shared hosting is enough for a site of any size, without changing any server settings.
- The restore is checked before it touches anything. Every file in the archive is verified first, the database is loaded into temporary tables and swapped in one step, and
wp-config.phpis never overwritten. - Nothing is locked. Every feature described here works fully in this plugin, with no account and no service of ours in between. Your backups stay on your server.
- PHP 7.4 or newer, 64-bit, with the zip, zlib and pdo_mysql extensions (present on almost every host).
- MySQL or MariaDB.
- Single sites. Multisite networks are not supported yet. == External services ==
安装:
- Upload the plugin and activate it.
- Open Restora in the admin menu and press Create backup.
常见问题:
Where are the backups stored?
In wp-content/restora-<random key>/. Its name cannot be guessed, and on Apache and IIS the files Restora puts in it deny web access. nginx ignores those files: Restora checks once a day whether the folder can be reached from the web and, if it can, shows the line to add to the nginx configuration.
What happens to my backups if I delete the plugin?
They stay where they are. Install Restora again and it finds them.
What is left out of a backup?
Cache folders, WordPress upgrade leftovers and the backup folders of other backup plugins. You can add your own paths and patterns in the settings; developers can also use the restora_exclude filter.
From the database, the tables of the site are backed up: WordPress's own, plus any other tables you choose in the settings. Views, triggers, stored procedures and events are not; WordPress does not use them, but some custom code does.
What happens if a restore stops halfway?
It is undone. Before a file is replaced, its current version is set aside, and the database is only switched over at the very end. If the restore cannot finish (the disk fills up, a folder cannot be written, the window is closed), every file goes back to how it was and the database is left untouched. Before anything is written, Restora also checks that the folders are writable and that there is enough free space.
What if the site is down and I cannot reach wp-admin?
A Restora backup is a normal zip, so nothing is locked in. The files are in it as they were on the site, and the database is plain SQL under .restora/ inside the archive: unpack the files over the site with FTP or the host's file manager, import the SQL with phpMyAdmin, and the site is back. The step-by-step guide is at https://restora.perforks.com/docs#restore-by-hand. Restora Pro adds an emergency recovery page that does all this for you, even when WordPress itself does not load, and copies of your backups on S3 or SFTP for the day the whole server is gone.
Who can run, download or delete backups?
Only administrators (network administrators on a multisite network): every screen, button and download checks that capability and a nonce, and the backup folder itself has a random name and is closed to the web, so a backup can only be fetched through Restora by someone logged in with that right. The restora_capability filter narrows the circle further, to a custom capability you give to the people you choose. The WP-CLI commands run only for someone with shell access to the server as the site's own user, who could reach the files anyway; define( 'RESTORA_DISABLE_CLI', true ) in wp-config.php switches them off on a server where that shell is shared. Restora Pro's remote access is read-and-run only: another site with the access key can list, start and download backups, never delete or restore; the key is stored hashed and locks after a few wrong attempts.
Do scheduled backups need a real cron job?
No. They start through WP-Cron and then keep themselves going. On a site with very few visits they may start late; a server cron job calling wp-cron.php makes the timing exact.
Does Restora create files outside its own folders?
No. Everything it writes stays in its own randomly named folder in wp-content. While a restore runs, its settings file waits there too (readable by the site only, and without the database credentials, which are read from wp-config.php) and is removed when the restore ends.
Can it restore an encrypted backup?
Yes. Backups encrypted by Restora Pro can be restored here with their password, even without Pro. A lost password cannot be recovered: that is what the encryption is for.
Can it back up before an update?
Yes. Under Settings, turn on "Before updates": just before WordPress updates a plugin, a theme or itself, Restora backs up the database, or the database with the plugins and themes folders if you choose so. Media is never included, because the update waits for the backup. One backup covers all the updates of the next ten minutes, the newest few are kept, and a backup that fails never stops the update.
Does it have WP-CLI commands?
Yes: wp restora backup, wp restora list, wp restora restore <name>, wp restora delete <name>, wp restora log <name> and wp restora status. Run wp help restora for the options. status exits with 1 when the backups need attention.
Does it work with multisite?
With Restora Pro, yes, site by site. The main site's backup carries the network itself (its tables, the user list, the shared files); every other site's backup carries that site's tables, its uploads and the users who belong to it. "All sites" makes one backup per site in one set, so the whole network goes back with one click, main site first, and restoring one site touches only that site and merges its users. The free plugin says so and stops on a network.
Does a restore delete files?
No. Files that exist on the site but not in the backup are left in place, and wp-config.php is never overwritten.
更新日志:
- New setting "Backups of other plugins": Restora finds the backups kept on the site by Duplicator, UpdraftPlus, All-in-One WP Migration, WPvivid, Backup Migration, BackWPup, Solid Backups and WP-DB-Backup, reads their folders from those plugins' own settings, and shows each one with its size. Ticked ones are left out of file backups; untick one to include it.
- Fix: the backups of current versions of Duplicator (the duplicator-backups folder) went into file backups.
- Fix: a scheduled backup was given up with "The job stopped responding and was abandoned" when the host stopped PHP in the middle of a step. The next step is now booked before each one starts, so a step that was stopped is repeated and the backup carries on from its last checkpoint.
- Upload a backup: bring a site back from a backup on your computer, for instance on a new, empty WordPress after the old site was lost. The file goes up in pieces sized to the server's limits and to the connection, so backups of 10 or 20 GB upload on any host; if the page is closed or the connection drops, choosing the same file again carries on from where it stopped. The backup is then listed like any other and restored in short steps, moved to the new site's address.
- A restore that is cut off half-way (window closed, computer or connection down, power cut) can be carried on from any window with "Carry on here", from its last checkpoint, or undone with "Undo the restore": every file it replaced goes back, and the database, which a restore changes only in its last step, stays as it was. Left alone, it is undone on its own after three hours. Maintenance mode lifts about two minutes after a restore stops, so the admin opens again to choose.
- Fix: a restore running for more than six hours (a very large site on a slow host) was cut off, and could then no longer be undone. Its key now lasts as long as the restore moves.
- The restore engine can restore some tables of a backup's database and leave the others as they are. Restora Pro uses this to restore chosen tables only.
- Security: a restore accepts from a backup's database only what Restora itself writes: plain rows of values and plain table definitions. Copying from other databases, reaching other servers or folders (FEDERATED, CONNECT, DATA DIRECTORY) and statements of any other kind are refused before anything changes.
- Security: file names with control characters are refused, and names that would reach a protected file by another spelling (a doubled slash, a Windows short name) are skipped.
- Security: the database connection uses only character sets in which quoting is safe, and every request of a restore checks that the archive is still the one verified at its start.
- Writing encrypted backups is now done entirely by Restora Pro; Restora itself writes plain backups and, as before, restores encrypted ones with their password. For developers: the zip writer takes a cipher through the new
restora_zip_cipherfilter, andrestora_backup_seallets it sign the archive index. - The reminder to turn on a backup schedule now appears only on the Plugins screen and on Restora's own screen, no longer on the Dashboard.
- The restore engine can check a whole backup without writing anything, and moves the addresses of every site of a network that moves with it. Restora Pro's installer uses this to move a whole multisite network.
- A multisite network keeps each site's roles when its table prefix changes in a restore.
- WP-CLI records which sites belong to an "all sites" backup of a network.
- Changing a schedule no longer starts it over. The next backup still counts from the last scheduled one; if that date has already gone by (a backup five days ago, now every three days), it is the chosen time's next turn. Intervals are counted in days, so moving the time after a backup no longer gives a second backup the same day.
- Under each schedule, a line says when it will run next, how often, and what it counts from, and follows the choices on the screen before you save.
- A downloaded backup is named after its site (yoursite.com-restora-full-....zip). A file with such a name copied back into the backup folder is recognised again.
- Security: the restore engine also treats a backslash as a folder separator on Windows servers, so a crafted archive cannot write outside the site there.
- On nginx, the notice about the backup folder now says plainly what is going on, shows the exact line for this site (with its real folder name and path, also for a site in a subfolder), explains where to paste it in CloudPanel, Plesk and similar panels, and has a Check again button instead of waiting a day.
- The Restora Pro card names Repair, which finds the plugin or theme that took a site down and fixes just that.
- Schedules can run every 2 or 3 days, every 2 weeks or every 15 days, next to every day, week and month. Site Health adjusts its "newest backup is too old" check to the schedule that is on.
- The restore engine can restore only chosen files or folders from a backup, checking just those, and can remove from plugins, must-use plugins and themes whatever the backup does not have. Restora Pro's emergency recovery page uses both: a file added after the backup is the usual reason a site stops working, and a targeted restore brings a single plugin back in seconds on a site with gigabytes of uploads. The restore from the Restora screen is unchanged.
- The Restora Pro card at the end of the screen now links to Restora Pro, and the Plugins screen has a Backups link (and a Get Pro link while Pro is not installed). Nothing else changes; the free plugin asks for nothing.
- Scheduled backups can start at any minute of the hour, not only on the hour.
- A
restora_capabilityfilter, to narrow who may use Restora to a capability of your choosing, andRESTORA_DISABLE_CLIto switch the WP-CLI commands off on a server whose shell is shared.
- Multisite networks: the hooks Restora Pro 1.2.0 uses to back up and restore a network site by site (which tables and folders a backup takes, which rows, a follow-up job after a backup, a merge step in the restore engine for the shared user tables). The free plugin still says so when a network needs Pro.
wp restora backup --site=<id|all>and a site column inwp restora liston networks.
- Details for every backup in the list: open a backup to see the site it came from, the WordPress, PHP and MySQL versions at the time, every database table with its rows, and the files grouped the way you think of them: each plugin and theme with its size, media uploads by year, and WordPress itself. Read from the archive's table of contents, so an encrypted backup is listed just the same.
- A guide to restoring by hand when wp-admin cannot be reached, linked from the Restore panel and the FAQ: a Restora backup is a normal zip with the database as plain SQL, so nothing is ever locked in.
- Restora Pro 1.1.0: Site Health and the Dashboard say when the emergency recovery page has not been set up yet.
- The plugin's home page link now points to https://restora.perforks.com.
- A backup before updates: when the setting is on, Restora backs up the database (and, if you choose, the plugins and themes) just before WordPress updates a plugin, a theme or itself, from the dashboard, from WP-CLI or automatically. One backup covers a whole batch of updates; the newest few are kept.
- WP-CLI:
wp restora backup,list,restore,delete,logandstatus, for scripts and for sites managed from the terminal.statusexits with 1 when the backups need attention, so it can sit in monitoring.
- Site Health now has a "Backups" check: it says whether a schedule is on, how old the newest backup is, and whether the last scheduled backup failed.
- A notice on the Dashboard and the Plugins screen when Restora is installed but no schedule is turned on. It can be dismissed.
- The log of every backup stays next to it: a Log link in the list opens it, long after the job itself is gone. When you write to us about a problem, that is the text to send.
- The list shows how long each backup took.
- Not enough disk space is reported as soon as the scan knows the size of the backup, with the numbers, instead of failing near the end.
- A backup started by hand that fails after its window was closed now sends the failure email too, when an address is set.
- The Download button shows that the server is preparing the file, and says when the download has begun; from there your browser shows the progress. Download all waits for each part to begin before asking for the next.
- Another WordPress site that shares the database is now recognised whatever its table prefix (a random one such as mttpiSq_ included). It is named under Settings › Other database tables instead of its tables being listed as if custom code had made them, and it is never backed up or restored with this site.
- The settings now say which prefix this site uses, as read from wp-config.php.
- When a backup or restore is cut off, a clear message now says what happened: the request was blocked, the server sent an unexpected page or an error, the connection dropped, the server stopped answering, or progress stalled.
- First release: resumable backups of the full site or of separate parts, restore with a safety backup, schedules and retention.