BackupRidge

BackupRidge is a WordPress backup plugin designed for reliability on every host. Full-site backups pause and resume across requests, so they complete even on shared hosting with strict time limits. Back up to local storage or remote providers, restore from any source, migrate another WordPress site into this one, and monitor everything from a clean admin dashboard.

Standard Features

• Resumable backups — Long-running backups save progress and resume from the last checkpoint so they finish on any host, including shared hosting with 30-second limits.
• Database backup — MySQL/MariaDB export via mysqldump (when available) or native PHP streaming with optional table filtering and row-level resumption.
• File backup — Back up wp-content (and optionally the full WordPress root) with exclusion patterns, compression, and optional archive splitting for large sites.
• Local storage — Store completed backups on the server filesystem. Optional subfolder under uploads (base: wp-content/uploads/backupridge).
• Remote storage — Add multiple destinations and upload completed backups to Amazon S3, Cloudflare R2, FTP, or SFTP.
• Scheduled backups — Run backups automatically on a daily, weekly, or custom schedule via WP-Cron, with a REST endpoint available for triggering from an external system cron.
• Restore — Restore from a local backup, remote storage, or an uploaded archive, with component-level selection (database, themes, plugins, uploads, core) so you only restore what you need.
• Site migration (receive) — Migrate another WordPress site into this one by uploading a BackupRidge migration archive from the Migrate admin page.
• Dashboard — View backup status, history, progress, and logs. Start, stop, continue, or retry backups from the admin UI.
• Backup watchdog — A cron-based watchdog recovers backups that stall due to missed cron events or loopback failures.
• Custom backup filenames — Choose a filename prefix (BackupRidge, site URL, or site name) with automatic date/time stamping.
• Multi-part downloads — Download each archive part from the dashboard, or use Download All to queue sequential direct downloads (reliable on shared hosting).
• Log viewer — Browse and download per-job log files directly from the admin UI.
• Webhook notifications — Optional HTTP POST after a successful and/or failed backup (you choose): generic JSON, Slack incoming webhook, or Discord webhook format; URL, format, and which outcomes to notify are in Settings.
• Update-screen warning — See a notice on WordPress update screens when no backup has been created in the last 24 hours.

Advanced Features

• More cloud providers + OAuth — Connect Google Drive, Dropbox, OneDrive, and Backblaze B2 with easy OAuth sign-in—no manual API keys required.
• Incremental backups — Only back up files that changed since the last run, reducing time and storage.
• Archive encryption — AES-256-GCM authenticated encryption for backup archives before upload (legacy AES-256-CBC archives are still decryptable for restore).
• Advanced scheduling — Multiple independent schedules with time-of-day, day-of-week, 5-field cron expression support, and per-schedule settings overrides.
• Backup verification — SHA-256 integrity checks on every archive part after backup completes.
• System cron integration — Managed system cron setup and WP-CLI commands for triggering and automating backups, instead of relying on WP-Cron.
• Custom filename templates — Build filenames from placeholders ({type}, {seq}, and more) instead of a fixed prefix.

Requirements

PHP 8.0 or higher, WordPress 6.7 or higher. The backup directory (default wp-content/uploads/backupridge) must be writable by the web server.

External services

BackupRidge can upload backup archives to third-party cloud storage services configured by the user. No data is sent to any external service unless the user explicitly configures a storage provider. Links to backupridge.com and stavatech.no are informational website links and do not receive backup data from the plugin.

Amazon S3

Used to store backup archives via the S3 API. Signed requests with user-provided credentials and backup files are transmitted when the user configures S3 storage. * AWS Customer Agreement * AWS Privacy Notice

Cloudflare R2

Used to store backup archives via S3-compatible API calls. Signed requests with user-provided credentials and backup files are transmitted when the user configures R2 storage. * Cloudflare Terms * Cloudflare Privacy Policy

FTP

Used to upload backup archives to a host, port, and credentials supplied by the site administrator. Data is transmitted only when the user configures FTP storage. This connection targets a user-selected server endpoint (self-hosted or third-party chosen by the site owner), so no single provider Terms or Privacy policy applies.

SFTP

Used to upload backup archives over SSH file transfer to a host, port, and credentials (or key) supplied by the site administrator. Data is transmitted only when the user configures SFTP storage. This connection targets a user-selected server endpoint (self-hosted or third-party chosen by the site owner), so no single provider Terms or Privacy policy applies.

Google Drive (BackupRidge Advanced only)

Not included in the WordPress download. When installed separately, BackupRidge Advanced can upload backups via the Google Drive API using OAuth and user-granted access. Backup file data and metadata needed for the upload are sent to Google when the user configures this provider and runs a backup. Setup requires enabling the Google Drive API on your Google Cloud project (not only OAuth credentials). See https://backupridge.com/docs/cloud-storage#google-drive

• Google Terms of Service
• Google Privacy Policy

Dropbox (BackupRidge Advanced only)

Not included in the WordPress download. When installed separately, BackupRidge Advanced can upload backups via the Dropbox API using OAuth. Backup file data is sent to Dropbox when the user configures this provider and runs a backup. Setup requires enabling file permissions on your Dropbox app and clicking Submit in the Permissions tab before OAuth. See https://backupridge.com/docs/cloud-storage#dropbox

• Dropbox Terms
• Dropbox Privacy Policy

Microsoft OneDrive (BackupRidge Advanced only)

Not included in the WordPress download. When installed separately, BackupRidge Advanced can upload backups via Microsoft Graph / OneDrive using OAuth. Backup file data is sent to Microsoft when the user configures this provider and runs a backup. Setup requires an Azure app registration with a redirect URI of wp-admin/admin.php (no query string) and account types matching your Microsoft sign-in. See https://backupridge.com/docs/cloud-storage#onedrive

• Microsoft Services Agreement
• Microsoft Privacy Statement

Backblaze B2 (BackupRidge Advanced only)

Not included in the WordPress download. When installed separately, BackupRidge Advanced can upload backups to Backblaze B2 via the Backblaze B2 Native API. It calls https://api.backblazeb2.com to authorize the session with the user-provided Key ID and Application Key, then uploads the backup archive parts. Backup file data is sent to Backblaze only when the user configures this provider and runs a backup.

• Backblaze Terms of Service
• Backblaze Privacy Policy

HTTP webhooks (backup status)

When webhooks are enabled in Settings, the plugin can send an HTTP POST to the URL you provide after a backup succeeds and/or after it fails, depending on the checkboxes you set. Choices: generic JSON (job id, status, size, duration, timestamp), Slack incoming webhook (JSON with a text field), or Discord webhook (JSON with a content field). Data is sent only to your URL; the receiving service’s terms apply if you use Slack or Discord.

REST / cron trigger (this plugin)

Optional: a REST URL with a secret key can be called by system cron so the site can run backup segments without WP-Cron or loopback. Requests go only to the same WordPress site; no third party receives data unless the site owner configures something else.

Preferred authentication: send the key in the X-BackupRidge-Cron-Key request header. Legacy ?key= query authentication remains supported for compatibility, but query strings can be logged by proxies and web servers.

Source Code

This plugin ships its full, human-readable source. Every minified script in assets/js/dist/ has its un-minified source in assets/js/src/, and the minified stylesheet assets/css/admin.min.css has its source in assets/css/admin.css, inside the same plugin package, so each compiled file can be reviewed and rebuilt. No source is removed during packaging.

Build tools and steps to regenerate the compiled assets:

• Requirements: Node.js 18+ and npm.
• Install dependencies: npm install
• Build JS and CSS (terser minifies each assets/js/src/*.js into assets/js/dist/, and PostCSS/cssnano minifies assets/css/admin.css into assets/css/admin.min.css): npm run build

PHP dependencies are managed with Composer (composer install). No third-party JavaScript libraries are bundled in a minified-only form; all shipped scripts are first-party and their sources are included as described above.