Innovate | Connect | Transform
ContactService statusUSD $

GICT knowledge base

Back Up and Restore Webuzo or Legacy Bread Basket Data

Published

Webuzo/BreadbasketBackups

Older Bread Basket installations used Webuzo’s backup tools. This guide preserves that historical workflow while distinguishing current Webuzo features and actual backup scope. It does not promise that every current InterServer VPS includes this panel, license or automatic backups.

Choose the right backup type

The historical menu was Webuzo End-user Panel > Server Utilities > Webuzo Backup. Current Webuzo offers role/version-dependent backup configuration. Sign in through the trusted HTTPS address supplied for your installation rather than assuming one hostname or port fits every service.

  • Full: the historical tool covered the user’s home, domains, cron and supported database/mail/DNS components, with installed-service dependencies.
  • Home: the selected user’s home files, not automatically every external database or service.
  • Data/Database: supported database content; the older Data option was MySQL-specific, not a universal MongoDB backup.
  • Mail: the supported mail-account/message scope in that installed version, not proof that all contacts, calendars or mail-client settings are included.

Create and retain a recoverable artifact

Confirm the actual included data, destination, available space and applicable retention before starting Backup Now. Inspect the job logs and completed artifact, and keep an independently protected copy outside the server. Downloading, restoring and deleting are different actions; confirm the selected file before each one.

Do not clear the only failure logs while diagnosing a backup. A full disk or failed remote upload can leave a partial artifact. Compression integrity and a success email alone do not prove that the intended application can be recovered.

Restore deliberately

Preserve the current state, verify version/component compatibility and test in an isolated destination before approving a destructive replacement. Review logs and actual application/mail/database behavior afterward. A pre-incident backup does not automatically remove malicious access paths or prove that credentials are safe.

InterServer migration-service boundary

The former cross-panel/VPS migration promise is withdrawn. InterServer’s confirmed web-hosting migration scope is cPanel-to-cPanel or DirectAdmin-to-DirectAdmin only. VPS and dedicated-server migrations are not offered. A self-managed Webuzo backup/restore procedure is not an exception to that policy.

References: historical Webuzo backup scope and logs; current Webuzo backup documentation.

Reviewed October 15, 2026. Documentation review; no panel, customer backup, mail data or migration was accessed or executed.

Related guides

Account services are unavailable until the production backend is configured.