Ozeki WordPress Resilience
Ozeki Resilience: preserve supported WordPress content and confirmed history in Amazon S3, then reconstruct it on a prepared WordPress. WordPress.org submission candidate.
Install
Upload it under Plugins → Add New Plugin → Upload Plugin, then activate.
Install straight from GitHub with WP-CLI:
wp plugin install https://github.com/ozekihiroshi/ozeki-wordpress-resilience/releases/download/wporg-0.3.3-rc.8/ozeki-resilience-0.3.3.zipOzeki Resilience
0.3.3 rc.6 was accepted for review on October 28, 2026, and the response to the review email was sent. We are awaiting the reviewer’s response; WordPress.org publication is not approved. Current distribution status and ZIP availability.
Preserve the articles, images and inquiries your site has accumulated, so you can resume publishing and serving users after a cyberattack. Ozeki Resilience saves supported content and provides a path to recovering it on a separate WordPress.
English | 日本語
Keep a path to recovery after an attack
Losing a site should not mean losing the information and relationships built through it. Ozeki Resilience preserves articles, images, comments and supported inquiry and member information, then restores them on a separate WordPress so you can resume publishing and serving users.
Backup and restore prepare you to return a site to a captured state. Resilience prepares you to bring back the content needed to continue your work when restoring the attacked site as it stood is not an option. Its priority is preserving valuable content and making it usable again, rather than carrying over the entire original environment.
The scope balances the value of what is preserved with the work needed to handle and restore it safely. The tables below show what is saved and restored, and what you prepare separately on the destination.
The underlying idea is to separate the lifespan of information from that of the system that created it. The aim is to preserve articles, images and other content as independent information assets that remain understandable and usable even if the original system is lost, and from which a needed system can be reconstructed. Preserved originals have value independent of the recovery engine.
Install WordPress, themes and required plugins separately from trusted distributors before recovery, and activate the required plugins. Resilience restores information assets and their supported relationships; it does not install or activate software from S3. It keeps the destination theme selection. Unknown settings are reported without being applied.
| Item | Handling |
|---|---|
| WordPress core | Install fresh |
| Themes | Reinstall from trusted distributors |
| Plugins | Reinstall from trusted distributors |
| Posts and Pages | Recover from independent originals preserved in S3 |
| Images and attachments | Recover saved supported formats from S3 originals |
| Settings and metadata | Apply only recognized items selectively |
| Members, inquiries and tables | Recover according to the supported adapter rules |
Download and start
- Check current distribution status for installable ZIP availability. Use the ZIP and SHA-256 on that page; do not select an earlier review package or
Source code (zip). - Read the first-time setup guide and prepare AWS access.
- Install the ZIP, open Tools → Resilience, follow the preparation checklist, confirm storage access and create a trusted initial Baseline, then enable protection. Installing or activating alone does not protect a site.
Use the installable ZIP, not GitHub's source archive. Runtime libraries are bundled. No Python worker, SSH helper, external runtime kit, Docker or continuously running recovery server is required. Standard AWS SDK credentials must be available to PHP; the guide uses an EC2 instance role. AWS charges are separate.
Requirements and supported content
WordPress 6.4+, PHP 8.1+, ZipArchive, InnoDB and writable resource paths are required. Prepare a versioned S3 bucket and dedicated prefix, one writing site per prefix, and appropriate IAM permissions. Recovery requires a compatible WordPress release line, recorded plugin dependencies and private writable staging outside the web root. The controls follow your WordPress admin language: Japanese or English.
Markdown dependency: Native-only Baseline and recovery do not require Markdown Documents. If active it is included; if documents or _ozmd_source originals remain while inactive, capture stops before saving. For Markdown recovery, install and activate the recorded compatible version first (tested 0.1.1).
What remains and what you can recover
Restore successfully saved content through the recovery point you select. Integrations cover the plugins named in this table.
| What is preserved | What you can recover |
|---|---|
| Posts, Pages and local images | Body, supported images, publication state, categories, tags, featured images and related information needed to use the articles |
| Core comments | Comments and moderation state, including saved edits and deletions |
| Markdown documents | Source and supported relationships. Ozeki Markdown Documents 0.1.1 |
| Inquiry forms and received inquiries | Forms and the inquiries you received. Contact Form 7 6.2.3 / Flamingo 2.6.4 |
| Member access | Core subscriber information and supported fields, settings and viewing restrictions. WP-Members 3.5.8.1 |
| Tables | Table content, supported display settings and references. TablePress 3.4.1 |
| ACF free basic fields | Values, definitions and field keys for 15 basic types on posts/pages. ACF free 6.8.10. Create a new trusted Baseline including ACF after updating |
| Site appearance included in the initial capture | Supported presentation settings for the separately prepared theme; software names and versions help reinstallation |
Install the integration plugins you need separately. Versions above are the tested versions. Contact Form 7 6.2.3 requires PHP 8.3+. Source text can be up to 5 MiB and supported images up to 32 MiB.
What is excluded from recovery, and why
Preserving content is separate from carrying over the original site's administrative access and entire operating environment.
| Excluded from recovery | Reason and handling |
|---|---|
| Original administrator logins, active sessions, AWS and mail connection secrets | Use access prepared on the destination instead of carrying over the original environment's administrative access and connections. Supported core subscriber information is covered above |
| Server/PHP configuration, DNS and external service or CDN resources | These belong to the destination or external service. Prepare their configuration and protection through those systems |
| Plugin-specific features and data outside the coverage table, and arbitrary custom settings | Each needs dedicated support to restore its behavior safely. This product focuses on the scope listed above |
| Saved settings whose handling is not defined | To avoid bringing back unknown behavior, these are withheld from automatic application and listed in the result. Saved information remains in S3 |
Use backups or the relevant service's protection for assets outside this scope. Resilience preserves and restores the content needed to resume your site's work.
From preservation to resuming service
- Capture a trusted initial site state as a Baseline and enable protection.
- Save supported changes during daily use. A Checkpoint is a recovery point made from what has already been saved. Follow the change procedures after changes such as theme updates.
- When needed, prepare a separate WordPress and select the initial capture or recovery point and the changes to restore.
- Check the articles, images, inquiries and other content you need, along with items reported as not applied, then reopen the site and resume service.
Check completed saves under Save protection status. If operations remain pending, follow save resumption. Recovery also restores saved publication state, so restrict public access while checking the destination. When responding to an attack, select a trusted initial capture and the changes you decide to adopt.
The user guide covers schedules, retention and cleanup. See the recovery FAQ for details of recovery behavior.
Documentation and support
- Terms of use: license, operational roles, data, costs, warranty and liability
- Install and update, including migration from the old prerelease folder
- Recovery procedure and recovery FAQ
- Application rules and withheld information
- External-service and privacy disclosure
- Current distribution status and matching source
Problems or questions? Use GitHub Issues. For a bug, choose the English or Japanese report template and describe the operation, expected result, actual result and versions as far as you know. Questions can use a blank issue. Reports are public; omit credentials and private content.
After publication on WordPress.org, the plugin page's Support tab will also accept questions and bug reports. The rc.6 review response has been sent; we are awaiting the reviewer’s response. We track fixes in GitHub Issues; if a report is already on one service, link it from the other instead of repeating the details. WordPress.org review emails are separate from user support.
Existing verification records describe their specific builds and environments; they are linked from the candidate record, not additional installation requirements.
License. Ozeki Database Backup for S3 is an independent product.
Preparation: current setup checklist.
Releases
15 releases. Each count is every asset in that release; expand a row for the breakdown.