Troubleshooting Chada Backup

The backup never progresses past a step

Jobs advance in short time-boxed steps (20 seconds by default) kicked off by background requests and WP-Cron. If nothing moves:

• Check that your host allows loopback requests and that WP-Cron isn’t disabled (DISABLE_WP_CRON). If it is, run wp cron event run --due-now from a system cron, or drive the job runner directly with wp chada-backup tick.
• Open the live log on the Dashboard — the last line usually names the cause.
• Click Resume. Jobs checkpoint after every step, so resuming never repeats finished work.

“Upload timed out” on a remote destination

Run Test connection on the destination card. If the test passes but uploads still time out, lower the upload chunk size under Settings → Advanced (16 MB by default; Google Drive uses 8 MB chunks), then Resume the job — completed parts are not re-uploaded.

Not enough disk space

Chada Backup keeps a reserve of free disk for the site itself and will stop rather than fill the disk. Free space by lowering Retention → keep last for the local destination, excluding large folders or tables under Settings → Exclusions, or running wp chada-backup prune --keep=<n>.

A set shows as unverified

Verification compares every file’s SHA-256 checksum with the manifest. A mismatch usually means a file was altered or truncated in storage. Re-run verification with wp chada-backup list --verify; if the local copy is bad but a remote copy exists, restore from the remote (the plugin fetches it and re-verifies).

Import says an archive is missing

A set is complete only when every file listed in manifest.json is present. The import panel names the missing piece (for example uploads-part3.zip). Add it to the drop zone — files can arrive in any order — or copy it into the import folder and Scan for backups again.

The site is stuck in maintenance mode after a restore

Restores enable maintenance mode while the database is imported and remove it in the Finishing step. If a restore was interrupted, reopen Chada Backup → Dashboard and resume or undo it; either path clears maintenance mode. As a last resort delete the .maintenance file from the WordPress root.

A recovery point wasn’t captured before an update

Recovery points are Premium and only capture before updates, never fresh installs. The capture also has a time budget (90 seconds by default) so an update isn’t held up indefinitely — when the budget is exhausted the update proceeds and a notice explains that the capture was skipped. Raise the budget under Settings → Advanced if your site is large.

Premium features are locked even though I have a licence

Open Chada Backup → License. The screen states the reason: expired, suspended, revoked, or the marketplace was unreachable. Click Revalidate (or run wp chada-backup license revalidate). If your seat count is exhausted, deactivate a site you no longer use from My Account → Licenses.

Uninstalling

Deactivating keeps your backups and settings. By default uninstalling does too — turn on Settings → Advanced → Delete all data on uninstall if you want the plugin to remove its options and local backup folder when it is deleted. Backups stored on remote destinations are never deleted by uninstalling.

Still stuck?

Open a ticket from the Support page with the job log attached (copy it from the live log panel). Premium customers are routed to the priority queue automatically.