saas1980 :
This is precisely my concern, the wear and tear and constant heavy use of full backups. BTW cobian does not replace the previous full back, which has been my desired outcome. But as you you suggested it's ridiculous having to create full backups regularly when vast amount of the data remains the same.
The mirror image solution sounds brilliant and I will definitely look into this further. But currently im more concerned about the same concerns above (the example of file history I shared with mcnumpty). I understand incremental backups write over previous backups if changed, but is there way to keep those previous files too, like a secondary option? I have found many instances where I have saved documents in the past by deleting some needed content, especially in excel and word. Once saved and closed, office applications when opened again do not allow to revert back to the previous state. Hence I am able to revert back to my full backups to find those files. In some cases, the error may have been noticed several weeks later after several backups had commenced. Here with my current full backup weekly setup I am able to open my backup folder and locate all weekly full backups. All i need to do is locate the week in which the document contents were changed/deleted, open the file, copy and paste the missing/changed contents back to my current document.
Now I'm looking for an alternative to full backups, such as incremental, but I don't want the changed files to be overwritten and would need the same flexibility to revert back to the previous states.
Remember that a backup is useless if it goes up in flames with the PC... so offsite storage is recommended.
We use a BlacX HD dock and a series of HDs for this purpose and rotate them out in the course of a month.
Days 01 - 07 - SSHD No. 1
Days 08 - 14 - SSHD No. 2
Days 14 - 21 - SSHD No. 3
Days 22 - End - SSHD No. 4
In a mirror, files do not exist inside a big compressed backup files. It's no different from you doing "copy / paste". If you want versioning, you can Save the file as Resume 0, Resume 1, Resume 2 with each change. But this depends on your goals and this would be as "I wanna keep forever". In most business settings versions of draft documents are not kept. Once sent out, that file is kept ... forever.
I have never looked to recover a file version that is > a month old. In the 7 or 8 times it's happened, it was an "A crap, I just saved over the wrong file" moment, and the old file is restored within 2 minutes.
Like most businesses, we uses in documents that are expected to go thru several revisions. Most offices, create a file called say "Dagwood Contract 2017"... again all internal revisions before it goes out are meaningless and are not kept. Once Dagwood sees it and it is edited, the new files is called say "Dagwood Contract 2017 Rev 03-27-17"
Another way is let's say a cost proposal and it's 5 pages long... when doing a revision. Those 5 pages are copied to pages 6-10, the date is kept and a "(Revised 03-27-16)" is added under the original date. Now all versions of the file are in the single file which is much easier to keep track of. All subsequent correspondence can be kept in the same file.
To keep a versioning system as you describe requires on to remember countless dates or a tracking system which would require an inordinate amount of T & E to create and maintain. Creating