Backup

Backups in Vvveb allow you to save and restore the entire database as a single SQL file. This includes posts, products, users, orders, settings, custom fields, taxonomies, and any plugin‑defined tables. A backup represents a complete snapshot of your site’s content and configuration at a specific moment in time, making it essential for disaster recovery, migrations, and development workflows.

Regular backups protect your site from data loss caused by accidental deletion, failed updates, server issues, or security incidents. Restoring a backup returns the database to the exact state it was in when the backup was created.

How Backups Work

The backup tool exports the full database schema and data into a .sql file. This file can later be imported to restore the site. Backups can be created manually at any time or automatically if scheduled backups are enabled.

Backups include:

  • All content (posts, products, pages)
  • All user accounts and roles
  • All ecommerce data (orders, customers, carts)
  • All plugin tables and custom fields
  • All settings and configuration stored in the database

Backups do not include:

  • Uploaded media files (images, documents, videos)
  • Theme files
  • Plugin files
  • Custom code

These should be backed up separately at the file-system level.

Backup Storage Location

All generated backups are stored in:

storage/backups

This folder contains timestamped SQL files that can be downloaded, archived, or restored.

Because backups are stored on the same server, they should not be considered the only copy of your data. If the server fails, local backups may be lost as well.

Best Practices

A reliable backup strategy includes both frequency and redundancy. Several practices help ensure your data remains safe:

  • Create regular backups before major updates, theme changes, or plugin installations.
  • Enable automatic backups to ensure consistent protection without manual intervention.
  • Download backups to your local computer to keep an offline copy.
  • Use remote storage such as rsync, SFTP, or cloud storage to keep backups on a separate server.
  • Test restores periodically to confirm that backups are valid and restorable.
  • Keep multiple versions so you can roll back to different points in time if needed.

These practices reduce the risk of data loss and make recovery faster and more predictable.

Restoring a Backup

Restoring a backup replaces the current database with the contents of the selected SQL file. This action should be performed carefully, as it overwrites all existing data. Typical use cases include:

  • Recovering from accidental deletion
  • Undoing a failed update or migration
  • Cloning a site for development or staging
  • Moving a site to a new server

Before restoring, it is recommended to create a fresh backup of the current state.