Recovery options ยท reviewed 16 October 2026
Cleanup, replacement and restoration can work together.
These are possible recovery approaches. The right choice depends on what is affected and the condition of the information available.
Cleaning the affected installation
A focused cleanup may preserve current content and useful custom work. The plan still needs to identify affected files, content, accounts and relevant configuration, rather than removing only the visible symptom.
Replacing website components
Trusted copies of software components may be part of the recovery. Custom files and site-specific settings need separate attention so useful business work is not lost in a broad replacement.
Restoring a backup
A restore can provide a working starting point, but the proposed backup needs checking. Its date matters: a recovered version may omit recent content or orders. A backup can also contain an earlier problem, so restoration is not a substitute for reviewing the incident.
Questions to answer before choosing
| Question | Why it matters |
|---|---|
| What is known to be affected? | The recovery needs to cover the relevant components, not just a visible page. |
| Is there a usable trusted copy? | Software sources and backups need appropriate checks before use. |
| What changed after the backup? | Recent business data needs an explicit plan. |
| Which owner or provider action is needed? | Website work may depend on account or hosting decisions. |
Record the choice and the limits
The recovery plan should explain why the approach was chosen, what will be checked and what remains uncertain. See the recovery planning checklist or ask about the incident.