Innovate | Connect | Transform
ContactService statusUSD $

GICT knowledge base

Configure Total Upkeep Backups and Verify WordPress Recovery

Published

WordPress

BoldGrid’s backup plugin is now called Total Upkeep. It supports backup and recovery workflows, but its preflight checks, archive checks and optional update recovery are not proof that every possible failure will be detected or that every backup is clean and restorable.

Confirm version and install deliberately

In an authorized WordPress administrator session, locate the official Total Upkeep plugin, check compatibility and follow your normal installation/change process. Edition features and subscriptions change; the older fixed price and blanket licensing claims are not current purchasing guidance.

Create a backup with known scope

  1. Open Total Upkeep > Backup Archives and choose Backup Site Now, where exposed by the installed version.
  2. Enter a descriptive title/comment and choose full or custom file/database scope.
  3. Inspect include/exclude settings and any file preview. Confirm required uploads, custom files and extension tables are not omitted.
  4. Run the job and inspect its log and actual archive rather than treating a saved configuration as completion.

Schedule and protect storage

Open Total Upkeep > Settings > Backup Schedule, select the approved interval/time and verify the scheduler. Configure available Backup Storage locations, quotas and retention deliberately; do not assume the old default of five copies or the same remote providers apply to every edition.

Keep an independently protected copy outside the hosting account. Verify any remote upload and plan recovery of its credentials/keys. Do not infer encryption from compression or from a general premium-feature claim; inspect the protection actually configured for your archive.

Test recovery and contain side effects

Preserve the current site, then restore a trusted compatible archive into an isolated destination with outbound mail, payments and scheduled jobs contained. Check the intended files, database records, administrator access, media and relevant application behavior. A preflight or archive integrity result is useful but cannot establish complete application recovery.

Optional pre-update backup/automatic recovery covers a defined workflow; it is not a universal crash-prevention system. Recovery links or migration tokens should be treated as secrets. A plugin-assisted self-managed move does not expand InterServer’s matching-panel web-hosting migration scope, and VPS/dedicated migrations are not offered.

References: official Total Upkeep listing; schedule and storage controls; preflight scope; vendor recovery documentation.

Reviewed October 15, 2026. Documentation review; no plugin, archive, remote authorization or WordPress recovery was executed.

Related guides

Account services are unavailable until the production backend is configured.