Okleone Backups – Backup, Restore, Migrate, Encrypted Cloud Backups

On a fresh install, in a wpab-backups folder beside your web root when the server lets the plugin write there, which no web request can reach; otherwise in wp-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.

Okleone Backups ships an .htaccess and a web.config that 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's server { } 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.

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.php in the plugin folder decrypts an archive on any machine with PHP.

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.

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.

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.

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.