Encrypted Backups, Kept Away From Your Host.

You choose one of three scopes per site. Full site is the database plus plugins, themes, uploads, wp-config.php and .htaccess. Database only is posts, pages, orders, users and settings, with no files. Files only is plugins, themes, uploads, wp-config.php and .htaccess, with no database.

WordPress core (the version is recorded instead), cache folders and other backup plugins' folders, single files over 256 MB, symlinks and unreadable files (listed as skipped so you can see them), archive or SQL files over 1 MB in the WordPress root folder, and .git and node_modules folders.

No. After the first backup, only changed files are stored again. A file counts as changed when its size or modified time differs. The database is copied in full every time.

Backups are encrypted before they leave your site, with AES-256-GCM and a new random key for every backup, and kept in Protuno's cloud, away from your host. Protuno holds the keys. Only signed-in people with access to that site can see, download, restore or delete its backups.

You choose 7, 30 or 90 days. The default is 30. The newest complete backup is always kept, even past that period. Old backups are cleaned up after each backup and every hour.

Yes. The Backups page lists every site with its status, last backup, schedule and storage used, with totals for sites protected, backups stored and storage used, and Back up now and Open for each site.

Yes. Each completed backup has Files .zip and Database .sql.gz, named <site>-<date-time>-files.zip and <site>-<date-time>-database.sql.gz. They open in standard tools, and saved backups can be downloaded even when the site is offline.

The whole site, the database only, or the files only. A part that isn't in that backup is greyed out with "Not in this backup." Restores work by scope only, so a single file or a single post can't be restored on its own.

Before, Protuno takes a fresh full backup of the site as it is now. If that fails, the restore stops and nothing is changed. After the switch, Protuno checks the site loads, with 3 tries over about 16 seconds. If it loaded before and fails now, everything is put back automatically.

Yes. Anything added after the backup, such as new orders, comments and posts, will be lost. The restore window says so before you go ahead.

The site keeps running during the restore until the final switch, which takes a few seconds. A backup does not put the site in maintenance mode.

No. A restore needs Execute mode. On a Read only site you see: "This site is Read only. Switch it to Execute (top of the page) to restore." Backing up, scheduling, downloading and deleting all work in Read only.

No. Backups restore only to the same site they came from.

No. The connector user, application passwords and connector plugin are carried over. wp-config.php is only restored if its database settings match the live site. Otherwise the live copy is kept and a note explains why.

A single WordPress site connected to Protuno through the plugin, PHP on the host with ZipArchive, OpenSSL and zlib, a writable wp-content folder, and a connector that allows PHP. It also needs free disk space for the temporary files: about 1.1 times the site's file size, plus 512 MB.

No. Multisite networks are refused. Backups are for a single WordPress site.

Protuno checks disk space first. If the site doesn't have room for the temporary files, the backup stops with "Nothing was written."

You get an email, on by default, at the site owner's account email: "Backup failed for {site}". Short connection drops are retried automatically, up to 5 times. A failed backup cleans up after itself, and your earlier backups are not touched. Brain's inbox also raises "Backup failed" and "Backup overdue".

No. It is one job per site at a time. If a scheduled backup finds a backup or restore already running, it skips that slot.