- Dec 7, 2012
- 279
- 0
- 0
In the past I have always separated system files from user data, in order to back up each appropriately. So I'd partition my hard drive and go through the exercises moving my user directories onto D: . Then I'd take a full image of my C partition once or twice a month and incremental images of D: daily. I'd save enough image files that I could roll the OS back a couple of months. And the incrementals of the user data served as version history.
Then I got my surface pro 3 and it all seemed like too much unpaid IT labor
Besides I wanted to try the windows file history thing for versioning.
But I wanted to keep the imaging software I was using (Easeus) because it let me explore and copy files from the image file, whereas windows backup produced an opaque file. So I imaged the whole disk every couple of weeks and used FileHistory for versioning.
Then I contemplated rolling back windows, and realized I would also be rolling back my user files, and FileHistory wasn't going to work like a backup and let me restore all my files to their latest.
So my question is, how can I back up system and data appropriately without two partitions?
Then I got my surface pro 3 and it all seemed like too much unpaid IT labor

But I wanted to keep the imaging software I was using (Easeus) because it let me explore and copy files from the image file, whereas windows backup produced an opaque file. So I imaged the whole disk every couple of weeks and used FileHistory for versioning.
Then I contemplated rolling back windows, and realized I would also be rolling back my user files, and FileHistory wasn't going to work like a backup and let me restore all my files to their latest.
So my question is, how can I back up system and data appropriately without two partitions?