Where Macrium Backup Images Should Live Never on the Same Disk
The most common backup mistake is not software. It is geography: the image sits on the very disk it is supposed to protect. Here is where images should live, ranked honestly, and the simple layout that keeps them usable.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 6 minute read
🎥 Watch the full process in the video - Macrium Reflect image backup and clone, live on a real PC
Reflect will happily save an image anywhere you point it - including a folder on C: itself. That image still helps against a Windows problem: a bad update, a deleted system file. But against a dead disk it protects nothing, because the patient and the medicine die together. Location is the whole game.
Where the image lives - what it survives
Same disk, another partitionDisk death - NO
Second internal driveDisk death - YES, theft/fire - NO
External USB, always connectedDisk death - YES, ransomware - WEAK
External USB, unplugged after backupDisk death - YES, ransomware - STRONG
NAS in another room or officeDisk death - YES, one site disaster - PARTLY
Read down the list and the pattern is plain: separation is protection. The strongest copies are the ones the PC cannot reach.
1
The Same-Disk Trap, Stated Plainly
Two partitions are not two disks. C: and D: on one physical drive share one motor, one controller, one fate. An image on D: is a fine rollback point for software accidents - keep it for that if you like - but never let it be the only copy and call the PC backed up.
2
The Good Homes, Ranked
External USB drive - the default answer for one PC. Big, cheap, and it can be unplugged, which no internal drive can match.
Second internal drive - always available for scheduled jobs, survives the system disk dying, but shares the PC's power supply, theft and fire risks.
NAS - the office answer: central, capacious, reachable by rescue media, and it can hold several PCs' images in one managed place.
3
The 3-2-1 Shape, Home Edition
The classic rule is three copies, two different media, one off-site. The honest home version is simpler: scheduled images on the external drive, plus one copy of the newest full image somewhere the PC cannot touch - a second external drive kept elsewhere, or a cloud copy of the most important set. Two drives rotated weekly beat one heroic drive connected forever.
4
Folder Discipline That Keeps Sets Restorable
One folder per PC - ReflectBackups\Office-PC style - never a mixed pile from three machines
Do not rename .mrimg files by hand; Reflect finds its sets by its own naming and definition files
Keep the backup definition with the data: export it, because the schedule and retention live in that definition, not in the image files
🔴 The one-line test: if this disk died tonight, what would still exist tomorrow morning? Whatever the answer lists - that, and only that, is your backup.
🎥 Watch the Complete Video
See every click in Macrium Reflect - the image, the settings and the restore - live in the full video.
My D drive is a separate partition. Does that count as a separate disk?
No. Partitions divide one physical disk; they do not duplicate it. A disk failure, and most ransomware, takes every partition together. A second physical drive is the minimum real separation.
Is cloud storage alone enough for images?
Usually not as the only copy. A full image can exceed 100 GB, and restoring it over a home connection can take many hours - on the day you need it fastest. Cloud is an excellent second copy; local is the working one.
How many images should the drive hold?
Let retention answer by time, not count: about three to four weeks of history for most PCs - one full a week plus the dailies between them. Size the drive at roughly three to four times one full image and it will breathe.
This guide is based on the Technical Anshu video on Macrium Reflect 2026 image backup and clone. Stuck on a step? Ask in the video comments - you will get an answer there 🙏