Decide which websites, databases and mail must be recoverable. Check available storage and the restore method. A structure-only backup omits the actual website files, email messages and database tables.

1. Open Backups > Schedule and add a schedule. Choose an available frequency, backup type and destination.
2. Continue to the schedule details and set a monitored completion address, run time and applicable day. Confirm the server’s timezone.
3. Set Maximum Scheduled Backups to the number of retained copies you actually need. Estimate storage from completed backup sizes, not just the website’s visible page count.
4. Save the schedule and inspect the first completed archive and notification. Confirm all intended domains and data types are included.
5. Periodically test recovery in an isolated location and review both retention and destination capacity after the site grows.

New successful backups should appear on schedule with the intended history retained. Record a tested recovery point rather than relying only on a green scheduling screen.

Daily scheduling requires provider enablement; weekly and monthly choices may be the available defaults. If a run fails, inspect quota, destination access and notifications. Do not delete the last verified copy merely to make room for an untested replacement.

A copy on the same server shares many of the server’s failure risks. Keep a protected independent copy and confirm that your recovery procedure can use it.

• Sending a SiteWorx backup to a remote destination
• Creating a SiteWorx database and restricted application user
• Scheduling a SiteWorx cron task with useful output
• Changing SiteWorx file permissions for a specific application

• InterWorx: Backup Siteworx Account