Identify the backup date and whether it contains website files, email or databases. Take a fresh backup of the current state first. For an active shop, agree how changes made since the backup will be preserved before restoring its database.

1. Open Backups > Management and locate the exact partial backup. Check its name, timestamp and intended scope.
2. Put the affected application into an appropriate maintenance state if users could write new data during restoration. Keep unaffected services running where practical.
3. Choose Restore beside that package and read the overwrite confirmation. Continue only when the selected historical state is the one you intend to reinstate.
4. Wait for completion, then check the restored website, database or mailbox. Use application logs to distinguish a restore failure from an unrelated configuration problem.
5. Re-enable normal access after verifying the recovered content. Retain both the pre-restore backup and restored package until the recovery is accepted.

Test a representative page, sign-in and data record for a website, or expected folders and messages for email. Check dates and recent changes explicitly rather than assuming a working homepage proves completeness.

If a full backup has no supported restore action, contact support about the correct recovery path. Do not extract it over a live account arbitrarily. If the wrong snapshot was restored, stop further writes and recover from the fresh pre-restore backup with the appropriate scope.

• Creating and downloading a full SiteWorx backup
• Importing a database backup with phpMyAdmin
• Exporting a recoverable database backup in phpMyAdmin
• Restoring selected account data from a DirectAdmin backup

• InterWorx documentation