Documentation

Backups

Backups

Backups give you a recovery point before maintenance or data changes.

Backup types

Database backup
Captures WordPress database content.

Use it before database changes, content changes, migrations, or operations that primarily affect stored data.

Files backup
Captures site files such as plugins, themes, media, and other WordPress files.

Full backup
Captures both database and files.

Use a full backup when a change may affect multiple parts of the environment.

When to create a backup

Create or verify a recent backup before:

  • WordPress updates
  • PHP changes
  • Plugin updates
  • Theme updates
  • Major cleanup
  • Complex troubleshooting
  • Destructive maintenance

Create a manual backup

  1. Open the instance.
  2. Open Backup.
  3. Select the appropriate backup type.
  4. Start the backup.
  5. Wait for the operation to finish.
  6. Confirm that its status is successful.

Do not consider a backup usable merely because a backup row exists.

Backup history

Use history to review:

  • Backup type
  • Status
  • Creation time
  • Duration
  • Available file or restore action

Downloadable backups

Download a backup when you need an external copy for inspection, transfer, or additional retention.

Store downloaded backups according to your organization’s security requirements because WordPress backups can contain sensitive information.

Retained backups

CanaryWP can retain supported backup data for later recovery.

Retention should balance:

  • Recovery requirements
  • Storage consumption
  • Workspace policy
  • Data sensitivity

Restoring

A restore changes the instance.

Before restoring:

  • Confirm the instance.
  • Confirm the backup.
  • Check its date and type.
  • Understand what current data will be replaced.

After restoring:

  • Open the public site.
  • Check WP Admin.
  • Run Site Testing.
  • Review logs if anything behaves differently.

Backup failure

If a backup fails:

  1. Review the failure message.
  2. Check instance health.
  3. Check available storage and runtime state where applicable.
  4. Avoid making the risky change the backup was intended to protect.
  5. Retry only after the cause has been addressed.

Important

A successful backup is part of a recovery strategy; it is not proof that the site will remain compatible after an update.

You still need testing.

On this page