PrivateHostLab editorial ·
At a glance
| Axis | A full-site restoration | An application-level rollback |
|---|---|---|
| Scope | Restores files, database and configuration from a chosen recovery point. | Targets a known application change while preserving unrelated current data where possible. |
| Evidence needed | Requires a compatible, tested recovery set. | Requires an identified change and a safe path to reverse it. |
| Data impact | Can overwrite changes made after the recovery point. | Can leave a mismatch if database and files are not considered together. |
| Test path | Use an isolated restore target before production where possible. | Rehearse the rollback on a separate target before relying on it. |
What changes the decision
- Which files, database and configuration must move together?
- What is the acceptable data-loss boundary?
- Can the action be rehearsed separately?
Decision example
After a failed update, a team records the affected journey and compares a plugin rollback with a tested restore set. The client approver chooses the least disruptive option with known limits.
The honest verdict
Choose the smallest recovery action that has compatible evidence and client approval.
Neither method creates a guarantee of zero data loss or uninterrupted service.
Neither column is a PrivateHostLab product claim beyond the VPS catalog shown on service facts.