This could be on me for over-complicating things, but Macrium Reflect sees one of my drives as unformatted, so to perform a backup, it does the entire drive regardless of whether or not it's backing up real data. All other drives on the system are detected and backed up correctly. Even the backup of the affected drive is readable, and shows up as formatted correctly when I mount the backup.
There's actually two affected drives, but that just comes down to how I partitioned them.
- I have 4 HDDs which I set up as two two-way mirror Windows 10 "Storage Spaces" (so each storage space creates a two-way mirror using two drives).
- I then took the two newly created "drives" and created two striped partitions, each using half of each storage space.
- Ironically, I split these up like this for backup purposes; I want to back up one of these drives (E) and not the other (F).
- Both are formatted as NTFS.
Here's a screenshot from Reflect V6:
As shown above, Reflect sees these both as unformatted, so the backup takes up a huge amount of space. And I'd guess that every time I do an incremental, it'll take up all that space again.
Here are the drives in Windows Explorer:
From what I can tell, Reflect is supposed to be compatible with both Storage Spaces and dynamic volumes. What I've done here is create something that is similar to a RAID 10 array, but using Storage Spaces to create mirrored pair and then striping across those. Any ideas on how I can get this to work? Is there a file-based backup I can use reflect for rather than the normal drive-level one that might work?