Create a Webuzo account backup before a major change and as part of a regular recovery plan. Choose the backup scope deliberately, then keep a usable copy outside the hosting server.
IN THIS ARTICLE
Check access and requirements
Check free account and server staging space, the size of databases and mail, and your available backup destinations. Decide whether you need a full account archive or only home files, databases or mail. Protect archives because they can contain credentials and private customer information.
01 Create and store a Webuzo account backup
- Open Server Utilities > Backup & Restore in the end-user panel. Select the backup type required for the planned recovery.
- For a full account recovery point, choose Full Backup and review the included account data. A home-directory-only archive should not be assumed to contain a consistent database export.
- Select an available local or remote destination and a clearly identified location. Do not save a downloadable backup in the public website directory.
- Start the backup during an appropriate window. Avoid overlapping resource-intensive jobs and keep application-consistency requirements in mind for active databases.
- Watch the Logs tab until the process completes. Check the resulting archive name, date and plausible size before downloading or copying it elsewhere.
- Keep several dated recovery points according to your retention needs and perform a controlled test restore. Record which data was included and how to retrieve it if the original server is unavailable.
Is a full account backup a bootable server image?
No. It covers the account data supported by the Webuzo backup workflow. Document recovery of the operating system, panel, custom services and data stored outside that account separately.
Check the backup or recovered data
Confirm the backup is readable at the chosen destination and that its log reports success. Test restoration of representative files and database data in isolation. A file listed in the panel is not sufficient proof that it contains everything your application needs.
Resolve setup problems
If the task fails, inspect quota, temporary space, remote credentials and the backup log. Preserve a known-good older archive while retrying. Do not delete the only usable backup to free enough space for an unverified replacement.