Restoring a Single File vs a Whole System
Not every recovery is a full-blown disaster. Far more often someone simply needs one file or record back as it was yesterday. A good backup setup makes both the small everyday restore and the big whole-system rebuild straightforward.
This article explains the difference and why we plan for both.
The Everyday Restore
Recovering a single deleted document, image or record is the most common request by far. Granular backups let us pull back just that item without touching anything else.
The Full Rebuild
When a whole server is lost we restore everything from a complete backup. This is rarer but needs to be tested so it runs smoothly under pressure.
- Single file: fast, low risk, frequent.
- Whole system: slower, planned, infrequent.
- Both should be possible from the same backups.
Why Both Capabilities Matter
A backup setup built only for full rebuilds makes the common task — retrieving one lost item — slow and clumsy. One built only for single files leaves you exposed when a whole server dies. We make sure your backups support both, so the everyday request and the rare catastrophe are each handled well.
| Restore type | Frequency | Typical time |
|---|---|---|
| Single file | Common | Minutes |
| Whole system | Rare | Hours |
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.