Опис
Okleone Backups backs up your database and files into verified archives, restores them through a wizard that checks everything with a dry run first, and moves whole sites between domains without breaking serialized data. The features other plugins charge for are the point of the free version: encryption with a key only you hold, cloud storage connected in one click, and migration that actually works.
Backups
- Manual and scheduled backups, hourly to monthly, of your database, plugins, themes, uploads and other wp-content folders
- Built for large sites: archives are split into parts and written across many short requests, so a 4 GB site backs up on ordinary shared hosting where a single long request would be killed
- Every archive is checksum-verified after it is written, and again before it is restored
- Retention rules so old backups clean themselves up
- Email reports, either every backup or only the ones with a warning or an error
Encryption, free, with your key
Switch it on and every new backup is encrypted on your server with AES-256-GCM before it is stored anywhere, local disk included. You hold the recovery key; no storage provider, no host, and not Okleone Backups itself can read your archives. A standalone decrypt tool ships in the plugin folder, so even a site that no longer exists cannot lock you out of your own backups.
Cloud storage without developer accounts
Connect Dropbox or OneDrive by approving access on the provider’s own consent screen. No app registration, no API keys to paste: our relay holds the app credentials so you never have to create developer apps, and your files travel directly from your server to the provider.
Restores you can trust
The restore wizard verifies the archives, then runs a dry preflight that reports exactly what would change before anything does. A restore that is interrupted resumes instead of starting over. Pick single components, the database alone, or everything.
Migrate and clone
Move a site to a new domain: URLs, paths and table prefixes are rewritten safely, including inside serialized data, which is where most search-and-replace tools corrupt a site. Take a full backup on one site, bring the package to another by cloud storage or upload, and press Migrate. Both directions are free.
Housekeeping
Database cleanup (revisions, transients, orphaned rows), file cleanup that shows where your disk actually went, a cron viewer, site info for support requests, and settings export/import.
Premium
The premium build adds, on top of everything above: incremental file backups (after the first full, each run carries only what changed, and a restore replays the chain for you), a staging site on your own server, Rescue Protection (an emergency console that keeps working when WordPress will not load, with crash pages that email you recovery credentials), a restore point taken automatically before plugin, theme and core updates, Amazon S3, Google Drive, Azure Blob, SFTP, FTP and S3-compatible services as storage targets, and 1 GB of managed WP-AllBackup Storage in Germany with every licence.
Premium is a separate build, WP-AllBackup, from your account at wp-allbackup.fixit.biz; install it and your settings, schedules and restore points carry straight over.
External services
The free plugin works without any account: backups, restores, scheduling, encryption, migration and the cleanup tools all run entirely on your server and contact nobody.
Two optional features talk to external services, and only when you use them:
The WP-AllBackup auth relay and portal, when you connect Dropbox or OneDrive. Pressing Connect registers your site with our portal (portal.fixit.biz), which issues the site a token; the relay (relay.fixit.biz) uses that token to hand your site the provider’s access token after you approve access on the provider’s own consent screen. We hold the provider app credentials so you do not have to create developer apps; we never see your files. What is sent: your site URL, the plugin version, and the token exchange itself. The same portal validates a licence key if you enter one. Our privacy policy and terms describe both services.
Dropbox and Microsoft OneDrive, after you connect them. Backup archives are uploaded from your server directly to the provider’s API, and deletions run there when retention removes an old backup. Their terms apply to what you store: Dropbox privacy, Microsoft privacy.
Скріншоти
Встановлення
- Install through the WordPress plugins screen, or upload the plugin folder to
/wp-content/plugins/okleone-backups/. - Activate it through the Plugins screen.
- Open the backup menu and press Backup Now. The local backup directory works out of the box, automatic backups are off until you switch them on in the policy, and the Targets tab adds cloud destinations when you want them.
Часті питання
-
Where are backups stored?
-
On a fresh install, in a
wpab-backupsfolder beside your web root when the server lets the plugin write there, which no web request can reach; otherwise inwp-content/wp-allbackup-backups, protected from direct download. Settings > Backup directory shows the folder in use and lists the alternatives. Optionally on every connected remote storage target as well. -
How do I make sure my backups cannot be downloaded over the web?
-
Okleone Backups ships an
.htaccessand aweb.configthat block direct access on Apache and IIS, and it takes the world-readable bits off the folder and its files so a web server running as a different user cannot serve them. It also checks, from the plugin, whether the folder actually refuses a real HTTP request, and shows a warning if it does not.nginx, Caddy and LiteSpeed do not read
.htaccess, so on those you must add the rule yourself. For nginx, inside the site’sserver { }block:location ~* /wp-content/wp-allbackup-backups/ { deny all; return 403; }The most robust option on any server is to move the backup folder outside your web root entirely: set an absolute path in Settings under “Backup directory” and the archives you already have are moved with it. If your hosting gives you nothing above the web root, keep the default and add the server rule above.
-
Are my backups encrypted?
-
If you want them to be. Under Settings > Encryption, switch it on and every new backup is encrypted on your server before it goes anywhere, local disk included. You are shown a recovery key once; write it down somewhere that is not this site, because it is the only way to read these backups elsewhere and nobody, Okleone Backups included, can recover it for you. Restores decrypt as they read, and
bin/wpab-decrypt.phpin the plugin folder decrypts an archive on any machine with PHP. -
Do I need API keys for Dropbox or OneDrive?
-
No. Cloud connections run through the WP-AllBackup auth relay: you approve access in the provider’s own consent screen and tokens are delivered to your site server-to-server. See the External services section for exactly what travels where.
-
Yes, that is what the split-archive design is for. Archives are written in parts of a configurable size, one short request at a time, with the backup saved after every part; a request that is killed costs one part and the next request carries on. The same slicing applies to verification and uploads.
-
What is a full backup here, and what is incremental?
-
Every file backup the free plugin takes is a full one, so any backup can stand on its own and be migrated on its own. Incremental file backups, where each run after the first carries only what changed, are part of premium; a chain made there restores on any plan.
-
Can I restore a site that no longer loads?
-
That is Rescue Protection, part of the premium build: an emergency console installed under a randomized name that loads nothing from WordPress, plus crash pages that email you recovery credentials when the site goes down. The free plugin restores through wp-admin, and encrypted archives can always be decrypted off-site with the bundled tool.
-
What happens to my backups if I uninstall the plugin?
-
Backup archives are left untouched. Settings, history metadata and schedules are removed.
-
Incremental backups, staging, Rescue Protection, pre-update restore points, the S3, Google Drive, Azure, SFTP, FTP and S3-compatible targets, and 1 GB of managed storage. Premium is the WP-AllBackup build, from your account; install it and settings, schedules and restore points carry straight over.
Відгуки
Для цього плагіна немає відгуків.
Учасники та розробники
“Okleone Backups” — проект з відкритим вихідним кодом. В розвиток плагіну внесли свій вклад наступні учасники:
Учасники
Перекладіть “Okleone Backups” на вашу мову.
Цікавитесь розробкою?
Перегляньте код, перегляньте сховище SVN або підпишіться на журнал розробки за допомогою RSS.
Журнал змін
The full release history travels with the plugin and lives at wp-allbackup.fixit.biz.
3.16.11
- New: a fresh install keeps its backups beside the web root when the server allows it, and starts with automatic backups switched off and the daily cadence ready in the policy; Backup Now works meanwhile, and a policy saved before this release keeps running.
- Changed: storage types this build cannot use are greyed out in Add target, and the header no longer offers “Check for updates” (updates come from WordPress.org).
- Fixed: after the premium build takes over, the old menu link opens the right page instead of “not allowed”.
3.16.10
- Changed: the warning that backups can be downloaded over the web appears on the plugin’s own tabs only, links to the Backup directory setting, and has a Check again button.
- New: the Backup directory setting lists the places this server can keep backups, best first, and fills in the one you pick; a new directory is checked over the web as soon as it is saved, and a move waits for a running backup or restore.
- Fixed: “outside the web root” is measured against the folder the web server serves, so a site installed in a subdirectory is not told a folder beside wp-config.php is private.
- Fixed: with a licence active on this build, every premium screen kept selling plans; they now point at the premium build of WP-AllBackup in your account, which the licence carries over to.
- Fixed: other plugins’ notices were not kept off this plugin’s page.
3.16.9
- Fixed: in the premium build, a login-protected staging copy shows the pictures that content names by their address; the live site answers them from the copy’s private media folder to somebody signed in.
3.16.8
- Fixed: the originals a restore keeps before overwriting files are archived a batch at a time; 3.16.5 rewrote that archive after every file.
- Changed: a mu-plugin or drop-in set aside from another site’s package is kept inside a zip, a staged file waits under a non-executable name, and no database query spells placeholders into its text through a variable.
3.16.7
- Fixed: in the premium build, a staging copy of a site running WebP Express with “Reference webps that haven’t been converted yet” on showed its pictures missing; the copy now swaps in only a webp that exists and serves the original otherwise.
3.16.6
- Fixed: in the premium build, a staging copy made from a wp-config.php whose ABSPATH line sits under an if without braces never loaded WordPress; a define the copy must not keep is now removed as a whole statement, the config is checked with PHP’s parser before the copy is made, and a copy no longer shares a Redis object cache with the live site.
3.16.5
- Fixed: a restore no longer leaves a replaced file’s original copy as a loose file under wp-content; it goes into one zip per restore.
- Fixed: database cleanup queries build their WHERE clause as a literal at each call site, not a variable passed into wpdb::prepare().
3.16.4
- Fixed: in the premium build, a login-protected staging copy can be made on hosts where the folder above the web root is read-only, a copy that crashes is reported as a crash with the line from its own error log, and a copy gets its own object cache namespace.
3.16.3
- Fixed: in the premium build, a staging copy that links the uploads folder failed only after copying everything else on a host that has switched off PHP’s symlink(); the option is now refused before anything is written. A failed staging build can also send a diagnostic report, as a failed backup can.
3.16.2
- Changed: a build only ever deactivates itself. When this build and the premium build are installed together, the redundant copy steps aside on its own and an admin notice names which copy stepped aside and which carries on; no build ever switches off the other one, or any other plugin.
- Changed: every database query the plugin runs goes through WordPress’s prepared-statement API, with table and column names passed as identifier placeholders. WordPress 6.2 is now the minimum version, which is what introduced them.
3.16.1
- Changed: where the site keeps its things is now read in one place. The paths the plugin operates on, the WordPress root it archives, the content directory it restores into, the plugin folder it puts components back into, are read from WordPress in a single documented class, and the package refuses to build if any other file reads them directly. Behaviour is unchanged, including on sites with a relocated content or plugin directory.