New
#821
The only downside to incrementals I've found is that one has to have all them in addition to the previous full backup present to be able to do a restoration. Incrementals backup only data changed or added since the last backup, be it a full backup or another incremental.
Differentials need only the last full backup and the latest differential to do a restoration. They backup only changes since the last full backup, even if other differentials were done before. The downside to differentials (as far as I can tell) is each one will be larger than the previous differential, eating up more and more disk space and taking more and more time to create.
Generally Differentials get larger with time but I have seen cases where they are not. Don't ask me why, I don't know.
While what you say is technically true, imaging remains the easiest way to backup data because keeping track of changes and deletions, as well as new data, is harder when just copying new data over to another disk. If maintaining a data base on a disk that never changes other than additions, then copying files for backups would work just fine and would be similar to cloning (cloning is something else that MR can do).
Frankly, I'm more concerned about losing data than I am the OS and programs. Although tedious and timeconsuming as all get out, an OS and programs can be rebuilt. Data, once gone, is usually gone forever. Being the lazy old broad I am, I prefer backing up everything.
You are better off with a program designed to backup data such as Microsoft's SyncToy or the one I use, FreeFileSync. These have the benefits of incremental backups but not the fragility of incremental images.
I have a 120 GB SSD for my C: drive. I put my data on a HDD. If I get a new program, I just install to the SSD, no streamlining. My SSD is about 35 GB. It is not that hard unless you just go crazy installing programs.
I'm thinkin' it depends on how many changes have occurred between backups. I was making weekly full backups and differentials between but that was taking too much time so I'm switching to montly full backups and incrementals whenever I add new data or make changes I can't afford to lose. The two incrementals I made this morning (I keep duplicate backups on two HDDs at home; a third is kept in a safe deposit box at my credit union and it gets rotated out no less than once a month) took only around fifteen minutes for both. Full backups take almost three hours.
I'm not worried about losing any of the incrementals between backups because I keep each full back up and its incrementals in it's own folder on the HDD it is stored on. I cross reference them with the associated xml file by naming the folder and xml with the date of the full back up (I add an a or b to the end of the date so I can keep the two backups separate). When I need more room on the HDD for another backup, I delete the oldest folder.
Each to their own. However, I would recommend to others substantially more than 25GB. On a 1TB spinner I'd go for 50-100GB. This gives you plenty of room for adding software you didn't envisage. After all, 50-100GB out of 1TB is not that great.
I also wonder how performance is affected if you run a partition close to capacity (maybe fragmentation issues)?