1. Define the recovery scope
Identify files, database, email and the desired date. Restoration may remove changes made after the backup. For WooCommerce, record orders and payments received since that point; a shop needs a recovery plan before rolling back.
2. Check the backup
Confirm date, contents and readability. An SQL export alone has no website files. DirectAdmin account backups, Installatron backups and WordPress plugin archives use different tools. Choose the process matching the format, not just the filename.
3. Preserve the current state
Copy current files and database before replacing anything. Store downloaded archives privately outside the public website directory. Schedule the work and pause changes when necessary.
4. Use the matching restore tool
For a DirectAdmin user archive, open Advanced Features → Create/Restore Backups if available. Select the recognised archive and required components, reviewing them before confirmation. For Installatron backups, use that application’s restore function in Installatron. Ask support when the format or access is unavailable. In Installatron, open My Backups, choose Restore, select the destination and review the files and tables that will be overwritten before confirming.
5. Validate the restored site
Wait for completion, then check:
- Public pages, login, media and plugins.
- Recent orders, customer accounts and consistency with provider payments.
- Forms, email, HTTPS and scheduled tasks.
6. When the backup is infected or incomplete
An older copy is not proof of a clean website. Compromise also requires cleaning and fixing the vulnerability. If data is missing, preserve current files and available logs to assess realistic recovery. Avoid repeated restores without diagnosis.
Related service
WordPress careOfficial documentation
Labels and options vary with versions, plugins and your account. Refer to publisher documentation for your configuration.