Use selective file restore when only identified files or folders need to return to an earlier state. This can limit disruption, but the selected files must remain compatible with the site's current database and application version.
IN THIS ARTICLE
01 Restore a defined selection
- Identify the affected paths and a verified backup point from before the problem.
- Preserve the current affected files and record recent deployments.
- Open the site's Restore area, select the backup and choose its selective-restore option.
- Select only the required paths and review the confirmation carefully.
- Start the restore, wait for completion and test the relevant page or function.
02 Check dependencies
A plugin or application update may change both files and database structure. Replacing only one part can leave the application inconsistent. Ask the developer whether a coordinated rollback is needed before restoring a whole software directory.
Common questions
Will this restore the database too?
A selective file operation should not be assumed to restore database content. Review the chosen action's scope and handle the database separately where needed.
Should I restore every file after an infection?
Choose a known clean point and investigate the entry route. A restore alone may leave the vulnerable component or stolen credential that caused the infection.
What if the restore cannot write files?
Check the saved connection and required write permissions. Download the selected backup for a controlled manual recovery if that is the appropriate supported alternative.
After verification, clear only the relevant cache and test as a visitor. Record the restored paths, backup timestamp and result. Keep the preserved current copy until acceptance so an unintended change can be investigated without guessing what was overwritten.