For most home and small business PCs, keep at least 30 daily backup versions and 12 monthly versions. That lets you undo a mistake from last week and still reach a file as it was months ago. If you back up hourly, keep the hourly versions for a day or two. Add a yearly version if you need long history for records. With incremental backups, which only store changes, this usually takes far less space than people expect.
Below is why version history matters, how the common retention schemes work, and how to pick the right numbers for your data.
Why keep more than one version?
If your backup only holds the latest copy of each file, it protects you against one thing: losing the whole drive today. It does not help when:
- You overwrite a document and notice a week later.
- A file becomes corrupted and the backup copies the corrupted version.
- Ransomware encrypts your files and the next backup saves the encrypted ones.
- You delete a folder you thought you did not need, and want it back next month.
- A website is hacked, and the attack is only noticed weeks later.
In each case you need a version from before the problem. The longer the problem can go unnoticed, the further back your history must reach.
Common retention schemes
Keep the last N versions
The simplest rule: keep the last 7, 14 or 30 backups. Easy to understand, but with daily backups, 30 versions only reaches back a month.
Keep everything for N days
Similar, but based on age. File History works like this, with options from one month to forever, or "until space is needed".
Grandfather-father-son (GFS)
The scheme most businesses use. It keeps three tiers:
| Tier | Taken | Typical number kept | Reaches back |
|---|---|---|---|
| Son (daily) | Every day | 7 to 30 | 1 week to 1 month |
| Father (weekly) | One per week | 4 to 8 | 1 to 2 months |
| Grandfather (monthly) | One per month | 12 or more | A year or more |
You get fine detail for recent days and coarser detail further back, which matches how people actually need restores: most are from the last few days, a few are from months ago.
Suggested retention by situation
| Situation | Files | System image |
|---|---|---|
| Home PC, photos and documents | 30 daily, 12 monthly | 2 to 4 recent images |
| Working from home | 48 hourly, 30 daily, 12 monthly | 7 daily or 4 weekly |
| Small business PC | 30 daily, 8 weekly, 12 monthly, plus yearly if records require it | 7 daily, 4 weekly |
| Website and database | 30 daily, 12 monthly | Not applicable |
| Photo or video archive that rarely changes | 14 daily, 12 monthly | Optional |
System images need fewer versions than files. You restore an image to get a working PC back, and the most recent good one is usually what you want. Files are where long history pays off.
If you work with regulated data, such as financial or health records, check what retention your industry or country requires. Some rules set a minimum; data protection laws can also set a maximum for personal data.
How much space does retention use?
With full backups, every version is a complete copy, so 30 versions of 200 GB would need 6 TB. Nobody does that. Modern backups are incremental: after the first full backup, each new version only stores what changed. Space depends on:
- How much data you have (the first full backup).
- How much changes each day, which for most people is a small fraction of the total.
- How far back you keep versions.
- Compression, which helps with documents and databases, much less with photos and videos.
As an example, 300 GB of data changing by about 2 GB per day, kept for 30 daily and 12 monthly versions, needs roughly the original 300 GB plus the changes kept over that period, not 42 times 300 GB. Our guide to how much space you need for a backup shows how to work it out. The difference between incremental and differential backups also affects space; see incremental vs differential backup.
Setting retention in Windows' built-in tools
- File History: Control Panel → File History → Advanced settings → Keep saved versions. "Forever" is the default; "1 year" or "Until space is needed" is more practical. Clean up versions removes older ones by hand.
- Backup and Restore (Windows 7): click Manage space to view or delete file backups, and choose whether to keep only the latest system image or let Windows manage image space.
- wbadmin: keeps older images on a local drive until space runs out; there is no setting for a fixed number.
None of these offer a true GFS scheme, and "until space is needed" means your history shrinks without warning as the drive fills.
Retention in Rocket Backups
Rocket Backups lets you set retention rules per job, such as keep 30 daily and 12 monthly versions, and clears out older versions automatically, so the backup drive does not fill up. Backups are incremental and compressed, which keeps the space for that history low. When you need to go back, you pick a date on the timeline and browse the backup as it was. For example, Rocket Backups lets you set a website job to keep 30 nights and a system image job to keep four weekly images, each with its own rules.
Retention mistakes to avoid
- Keeping forever by default. The drive fills, backups start failing, and you only notice when you need one. Set a limit you can afford.
- Cutting history to save space. Shortening retention from 30 days to 7 to free space removes exactly the versions that protect you from slow problems. A larger drive is cheaper than lost work.
- One retention rule for everything. Work files that change hourly and a photo archive that rarely changes need different settings.
- Forgetting the second copy. Long history on one drive is still one drive. Keep an offsite or offline copy too, in line with the 3-2-1 backup rule.
Choosing your numbers
- Ask how long a problem could go unnoticed. For most people it is weeks, which argues for at least 30 days.
- Add monthly versions for slow-burn problems and things you deleted deliberately and regret later.
- Check you have space for it, and buy a bigger drive rather than cutting history.
- Review once a year, or when your data changes a lot.
Frequently asked questions
What is grandfather-father-son backup rotation?
A retention scheme that keeps daily (son), weekly (father) and monthly (grandfather) versions, giving long history without keeping every daily copy.
Why keep monthly backups if I back up daily?
Some problems, like a corrupted file or slow ransomware, are only noticed weeks later. Monthly versions let you reach further back.
Do more versions mean much more space?
Not with incremental backups, which store only changes. Space grows with how much your data changes, not the number of versions.
