Most backup failures come down to one thing: the server killed the job before it finished. BackupEase is built to avoid that by adapting to your host. This reference explains how the engine works and which reliability settings to reach for when a backup will not complete.

Two ways to process a backup

BackupEase picks the fastest method your server allows and falls back gracefully when it cannot:

  • WP-CLI mode: when the server allows it, BackupEase probes for exec() support and uses WP-CLI to run work as a background process. This is the fastest and most reliable path.
  • Chunked PHP mode: when WP-CLI or exec() is not available, BackupEase falls back to processing the backup in small chunks over normal PHP requests, so it still completes on locked-down or shared hosting.

Detection is automatic, you do not have to choose. The dashboard reports which method a given backup used.

Aggressiveness levels

Aggressiveness controls how much work BackupEase attempts per step. Higher is faster but demands more from the server; lower is gentler and more resilient on constrained hosts.

LowSmallest steps, lightest server load. Best for strict shared hosting or when higher settings time out.
MediumA balanced default that works on most hosts.
HighLargest steps, fastest backups. Best for VPS, dedicated, or managed hosts with generous limits.

Per-step time-limit tuning

Each processing step runs under a time limit chosen to stay safely inside your server's execution cap. If steps are being cut off, lowering the per-step time limit (so each step ends before the server intervenes) often makes a backup that kept failing run cleanly to the end.

Resource-exhaustion guards

The engine watches memory and execution time as it runs and backs off before it hits a hard limit, pausing and resuming rather than crashing mid-archive. This is what lets large sites finish on modest hosting instead of failing partway through.

Suggested settings by host type

Host type Likely mode Aggressiveness
Strict shared hosting Chunked PHP Low
Typical shared / business hosting Either Medium
VPS, dedicated, or managed WordPress WP-CLI High
If a backup keeps timing out

Lower the aggressiveness one level and, if needed, reduce the per-step time limit. Then run a manual backup to confirm it completes before trusting a schedule to the new settings.

Scheduling reliability: use a real cron

WordPress schedules run on WP-Cron, which only fires when your site receives a visit. On a low-traffic site that can delay a scheduled backup. For exact timing, disable WP-Cron and call it from a real server cron job instead:

  • Add define('DISABLE_WP_CRON', true); to wp-config.php.
  • Create a server cron job that requests wp-cron.php on your schedule (for example every 5 minutes), or triggers WP-Cron with WP-CLI.
Test after editing wp-config.php

Editing wp-config.php affects the whole site. Make a backup first, change one thing at a time, and confirm both the site and a manual backup still work before you rely on the new cron.