Not dumb at all.
Incremental and differential backups start with a full image and then for subsequent runs just record the differences and so create smaller backups. In the case of incremental each backup starts at the full image and works through a chain of incremental images so many files can be involved. Differential backups always difference from the base image so only two files are involved.
Hope that makes sense.
Not really, can you give me an example. Say Day 1 you put the basic as 2 GB (Office and COD4). On Day 2 you add to the basic COD3 and COD2? Is this correct?
Ok.
Incremental.
base Image->inc 1->inc 2->inc 3 etc.
Diferential.
base image->dif 1
|
+->dif 2
|
+->dif 3 etc
So the incremental relies on the base plus all incrementals.
each differential relies only on the base.
Kado897 can followup this.
But I would steer away from them for general system backups. Why- increase points of failure.
Windows Imaging does a slightly different thing. It stores the most current image and retains backward differences in shadow storage. I use Windows image with great success but NOT difference images. Just make one image, delete, or rename.
I would support Macrium Reflect as a solid well proven product and use it also.
I find it useful to do a full image each week and differentials on the latest full image each day. This means that I can go to a full image that is only a maximum of a week old if necessary but have the convenience of a daily differential. I have restored from these several times without problems.
I found the article explaining the two.
v5: Incremental and differential disk images (Differential Image, Incremental Image, v5)
I had to do windows all over again. Not doing it again either. So someone told me about Macrium Reflect. So I downloaded it and followed the directions and up and running in no time. So my battle plan is to install two programs, run them and if the work the do an image of C. I put the image on D and then another one on my USB stick (32GB). However, I'm doing full images and they are taking like forever as I add programs to C. So which way do I go to make this process faster?
The speed of imaging depends on a number of things but primarily
1. how big is the disk you are imaging
2. The speed of your disk reads and writes.
A full image of C (90 GB) with Macrium takes 35minutes to a USB attached HDD creating an image file of 36GB.
A differential on that takes 10-15minutes and produces files from 500MB to 4GB depending on how much has changed.
The speed in my case is limited by the speed of USB.
Windows imaging does a form of "differential imaging" differently from Macrium as I stated and is definitely risky in my opinion.
Macrium differential imaging may be more reliable - I don't know. I would still stick with primary images. Macrium uses the normal differential imaging approach which adds the differential to a "parent" image. Hopefully if the differential gets corrupted, the parent remains in tact. Someone who has actually had this issue may care to comment.
A downside of Macrium Reflect is that from experience image recovery takes longer. This is why I still use Windows imaging. Both a full 50GB image and recovery take ~ 10 minutes each.
I thank you both and I think I'll stick with what I'm doing.
Quote