If you do lots of backups, then you will quickly run out of room to store them unless you do incrementals and fulls.
At my last job, we did an incremental backup every night; on Friday nights, we did a level 7 incremental backup; and on the first weekend of the month, we did a full backup. This was only for the hundreds of Windows and Linux servers that we backed up each night. Exchange and SQL backups were full backups every night.
At home, however, all I ever do is full backups. I do a full backup of each computer about once every month or two.
Comparing business backups to personal computer backups is much like comparing oranges to kumquats.
If you are imaging the entire computer, full or otherwise, then yes, you will quickly run out of room for the images. However, there are disadvantages to imaging the entire computer. First, there is the issue of running out of room for storing the images since the images will be enormous. Second, any data created since the last viable image will be lost in a restore. With incrementals, you must have the last full image plus all of the incrementals made since the last full backup. If one incremental should fail, you will lose all new or changed data since the incremental before the one that failed. Keeping track of which full and incremental images need to be kept together can become problematic.
It is better to keep data segregated from System files (OS and programs) and use imaging only for the System files. A typical setup would be to have the OS and programs only on the C: drive or partition and the data only on a separate drive and partition. Only the C: drive would get imaged.
The only time I image my C: drive is before making any changes (and sometimes afterwards; either can be done) to the OS or programs, such as installing updates, new programs, changing settings, etc. I keep only the last six weeks of images at a time, after which I only keep only the first image of each previous month.
Data, on the other hand, is best backed up using a folder/file syncing program such as SyncToy or
FreeFileSync. When set to Mirror (not the same as RAID 1, btw), these programs will compare the data drive or partition with the backup drive or partition (drives and partitions are treated the same as folders) and any data that has been added or changed on the data drive since the previous backup will be copied over to the backup drive or partition. Any data deleted from the from the backup drive or partition since the last backup will be deleted from the backup drive or partition. This results in a backup that is essentially an exact copy of the original drive or partition and takes up only the same amount of room as the original. Since only recently add, changed, and deleted files are involved in an update, the amount of time required to update a backup is dramatically reduced. This also has the advantage of being able to use the backup as is for a direct replacement of the original (in which case, it is advisable to have a duplicate backup already handy).
The better folder/file syncing programs have a feature called versioning which will send files deleted from the backup drive or partition to another drive, partition, or folder that you designate for the purpose. This protects you from losing data due to deletions caused by corruption of an original file or due to user error. This does require some added space but nowhere nearly as much as would be required by imaging.