Create and Restore BackWPup Backups with Current Version Controls

BackWPup can back up WordPress files and database content and restore supported backups. Its interface and edition features have changed since the older Jobs/Add New Job tutorial. Start with the maintained installed release rather than reproducing an obsolete menu or feature/price list.

Install and select the intended backup

Use Plugins > Add New with an authorized administrator, confirm the official BackWPup publisher and compatibility, then install/activate through your normal change process. Existing installations should follow the vendor’s supported upgrade path with an independently recoverable copy available first.

1. Open the current BackWPup dashboard and review its backup setup/onboarding or backup settings.
2. Select the file and database scope required for the site. A WordPress XML export or plugin list is not a complete database-and-files recovery set.
3. Choose the supported storage destination and inspect its actual account, path and permissions.
4. Start a manual backup, monitor the task/log and confirm the completed archive and any remote copy.

Scheduling is version-specific

BackWPup 5 introduced a substantially revised interface and moved legacy job/log controls under advanced settings. Do not expect the old five-tab Add New Job screen in every release. Use the current dashboard’s schedule controls or the documented advanced workflow applicable to your version.

Verify the chosen scheduler and an actual scheduled artifact. WordPress Cron can be delayed by the site’s execution environment; a saved time is not proof of execution. Protect any job-trigger link as a secret rather than publishing it or creating an unauthenticated administrative endpoint.

Check edition and protection boundaries

The current official listing distinguishes restoring a manually uploaded backup in the free edition from direct storage-destination restoration in Pro. Verify the installed release’s supported providers, multisite scope and encryption options before relying on them. The previous blanket automatic-restore, email-delivery, encryption and pricing promises are withdrawn.

Compression is not encryption. Keep a protected independent copy, verify retention and storage capacity, and retain needed keys outside the backed-up server. Do not assume that an emailed success report proves a complete remote archive.

Restore and verify deliberately

Preserve the current site and use a trusted compatible backup. Test restoration in isolation before overwriting production, containing outgoing mail, payments and scheduled integrations. Check actual records, media, plugins and permissions, then plan the loss/reconciliation of changes since the backup. Restoring an old archive is not a malware-removal guarantee.

A move to another domain/server requires separate URL and compatibility checks and is a self-managed procedure, not an InterServer VPS/dedicated migration offer.

Reference: official BackWPup listing, restore distinctions, release history and support links.

Reviewed October 15, 2026. Documentation review; no plugin upgrade, cloud transfer, scheduled backup or customer restore was executed.