Website disaster recovery
Stop making changes, record what happened and restore the smallest known-good backup that solves the problem
UKC shared hosting customers can restore their own Plesk Backup Manager copies or request help with UKC’s daily server-side backups. A restore can overwrite newer files, databases or mail, so define the affected service, desired restore point and acceptable data loss before proceeding.
What should you do immediately?
Stop publishing
Pause updates, deployments and automated jobs that could overwrite recoverable data or hide the cause.
Record symptoms and time
Note the first known problem, last known good time, affected URL, error and recent changes.
Check the scope
Determine whether the issue affects one page, files, a database, email, DNS or the whole account.
Change exposed credentials
If compromise is suspected, secure the Client Area, Plesk, FTP, database and administrator credentials from a clean device.
Which restore should you choose?
| Problem | Likely restore scope | Risk to check |
|---|---|---|
| Deleted or changed website files | Domain files or selected file copy | Newer uploads can be overwritten |
| Broken WordPress content or settings | Database, sometimes files too | Orders, comments or edits after the restore point can be lost |
| Mailbox data missing | Mailbox or mail data request | Current messages and folder state need careful handling |
| Widespread compromise | Known-good account components plus security cleanup | Restoring infected code without fixing entry point causes reinfection |
What should a recovery ticket include?
- 1Identify the service
Give the domain, assigned server and affected website, database or mailbox.
- 2Define the restore point
State the last known good date and time with the UK time zone.
- 3Define the scope
Say whether you need selected files, a database, mail or a broader account restore.
- 4Confirm overwrite awareness
Explain which newer data must be retained before any restore replaces it.
What should you do after restoring?
Test critical journeys
Check HTTPS, forms, login, orders, email delivery and recent content.
Patch the cause
Update vulnerable software, remove unknown users and fix insecure permissions or credentials.
Scan and monitor
Use WordPress Toolkit and Imunify tools where applicable, then watch logs and file changes.
Improve backups
Schedule Plesk backups appropriate to the rate of change and retain a suitable independent copy.
Recovery questions
Does UKC take backups?
UKC takes daily server-side backups for shared hosting and can handle restore requests. Customers can also automate and restore their own Plesk Backup Manager copies.
Is a restore guaranteed to contain every change?
No. It reflects the selected backup point and scope. Data created after that point may not be present.
Will restoring remove malware?
Only if the restore point is clean and the original entry route is fixed. Otherwise the problem can return.
Should I restore before investigating?
For an urgent outage, recovery and investigation may run together, but preserve useful evidence and avoid unnecessary broad overwrites.
Need a server-side restore?
Tell UKC exactly what, when and where to restore
Do not send passwords. Include the domain, server, scope and last known good time.