Setting up Demfilz Backup

What this plugin does

Demfilz Backup bundles your database and files into a single .zip and uploads it to your own Google Drive. Backups and restores run in small, resumable steps and transfers are chunked, so large sites finish without hitting PHP limits. You can back up on demand or on a daily, weekly or monthly schedule, and keep only the most recent copies.

Restoring a backup onto the same site (rollback / disaster recovery) is free. Restoring onto a different URL — moving or cloning a site to a new domain, with automatic serialization-safe URL rewriting — is provided by the separate Demfilz Backup Pro add-on ($19/year, all your sites).

Step 1 — Install & activate

• Install Demfilz Backup from the WordPress.org directory — in your dashboard go to Plugins → Add New and search “Demfilz Backup”, or download the zip from the directory.
• In WordPress admin, go to Plugins → Add New → Upload Plugin.
• Choose the downloaded .zip, click Install Now, then Activate.
• A new Backups item appears in the admin menu — everything below is under it.

Step 2 — Connect Google Drive

Go to Backups → Settings and click Connect with Google. Approve access in your Google account — no Google Cloud project or keys required. When you return, the connection shows as Connected with your account email.

• The plugin requests only Google's drive.file permission, so it can see and manage only the backup files it creates — never the rest of your Drive.
• Prefer to use your own Google app? Open Advanced → Use my own Google app, create an OAuth client (type: Web application) with the Google Drive API enabled, register the redirect URI shown, paste your Client ID and Secret, save, then click Connect. Nothing then passes through Demfilz.

Step 3 — Choose what to back up & run it

On Backups → Settings, under What to back up, tick what to include — database, uploads, themes, plugins and other wp-content (and optionally WordPress core). wp-config.php and the plugin's own backup folder are always excluded.

• On Backups → Backup & Restore, click Back up to Google Drive (or back up to the server only).
• Set a Schedule (daily / weekly / monthly) and a retention count to keep only the most recent N backups; older ones are pruned automatically.
• Optionally set an email report address to be notified after each scheduled backup.
• If a backup ever times out on a very strict host, lower Files per step and Database rows per step under Performance.

Step 4 — Restore (and migrate on Pro)

On Backups → Backup & Restore, pick a backup from the list (or upload a .zip) and click Restore. Confirm — restoring overwrites the current database and files, so keep a fresh backup first.

• Same site (free): leave the New site URL as this site's URL and restore — a straight rollback.
• Different URL (with the Pro add-on): with the Demfilz Backup Pro add-on installed and licensed, set New site URL to the new domain. It rewrites every occurrence of the backup's original URL — including inside serialized and page-builder data — so the restored site works on the new address. A changed table prefix is handled automatically.

Troubleshooting

• “Insufficient authentication scopes” on upload. The Google connection didn't include Drive access. Click Disconnect, then Connect with Google again and approve Drive access. (If you use your own Google app, add the drive.file scope to its consent screen first.)
• Backup built but upload failed. Your archive is still saved on the server (listed under “Your backups” as This server) — reconnect Drive and run the backup again.
• Large site. Backups are resumable; just let it run. If your host is very strict, reduce the per-step counts under Performance.