Innovate | Connect | Transform
ContactService statusUSD $

GICT knowledge base

Back Up and Restore PHPFusion Tables Without Losing Site Files

Published

BackupsPHP-Fusion

PHPFusion’s database backup controls export or restore selected database tables. They do not automatically preserve uploaded media, themes, infusions or every configuration file needed to reconstruct the site.

Identify the installation and backup scope

The older interface used System Admin > Database Backup with backup and restore sections. Newer layouts and development branches differ; match instructions to the installed release rather than treating a development repository as a production release recommendation.

  1. Use an authorized administrator session over HTTPS and locate the supported database-backup tool.
  2. Confirm the actual database and table prefix. Include required core and infusion tables, but avoid unrelated applications sharing the same database.
  3. Review filename and supported format/compression choices, generate the export and download a private copy.
  4. Record the release, time and selected tables, and preserve the matching application files and configuration separately.

Restoration changes live records

Do not treat Choose File > Restore as equivalent to uploading an image. The selected SQL can replace tables and data. Inspect the trusted backup’s expected format and prefix, preserve the current state, and test it in a compatible isolated installation before approving a production replacement.

Release-specific restore forms can offer table/prefix and data selections. An incomplete table set may leave records inconsistent even if a task reports success. Do not hand-edit prefixes or import arbitrary SQL without understanding its effects.

Verify the recovered site

Check administrator and ordinary-user access, representative content, infusion data, media and permissions. Keep outbound email and background jobs contained while testing. Upload/time/memory limits may make a panel or administrator-managed database method more appropriate for large backups; do not solve a failure by making backup directories world-writable.

Keep backup files and temporary restore material inaccessible to anonymous website requests. Preserve evidence and investigate the entry point if recovering after compromise; a database reset is not an assurance that malicious files or credentials are gone.

References: official PHPFusion repository and release selection; development implementation illustrating backup/restore scope, not a stable UI guarantee.

Reviewed October 15, 2026. Documentation/source review; no PHPFusion database, files or live form was restored or tested.

Related guides

Account services are unavailable until the production backend is configured.