Sorry, Dave, but I'm still not understanding from your explanation how SyncBackSE 'knows' what to incrementally back up if it doesn't compare X with Y. My mirrored backup dataset is over 500GB in size. If I were to create incremental backups of this entire set, I would be in hock for disk space very soon!
In an incremental backup, you only want what has changed in your dataset backed up - adds and edits (deleted files are obviously excluded). When I run my Mirror operation, SyncBackSE gives me this list of 'differences' between the Source set and the Target set. Other than Deletes (actually defined as files no longer present on the Source but still present on the Target), why couldn't the application be told to write the Adds and Edits to Target Z rather than replacing those in Mirror Y? Then, in the next go-round, the 'differences' function would examine Target Y *and* Target Z to create Target Z1, and the process repeats (up to a limited number of "Z's"). I suppose this is introducing architecture that SyncBackSE is not capable of, but could there be a way for the user to manually intervene when presented with the 'differences' and be able to copy them all out to a Z point?
Without this functionality, the only other way I see an incremental backup working is by creating profiles of data subsets that feature files which are normally edited (Word docs, etc.) and omit files that normally aren't (MP3's, etc.), even though the term 'normally' even here is a stretch.
Thanks.
In an incremental backup, you only want what has changed in your dataset backed up - adds and edits (deleted files are obviously excluded). When I run my Mirror operation, SyncBackSE gives me this list of 'differences' between the Source set and the Target set. Other than Deletes (actually defined as files no longer present on the Source but still present on the Target), why couldn't the application be told to write the Adds and Edits to Target Z rather than replacing those in Mirror Y? Then, in the next go-round, the 'differences' function would examine Target Y *and* Target Z to create Target Z1, and the process repeats (up to a limited number of "Z's"). I suppose this is introducing architecture that SyncBackSE is not capable of, but could there be a way for the user to manually intervene when presented with the 'differences' and be able to copy them all out to a Z point?
Without this functionality, the only other way I see an incremental backup working is by creating profiles of data subsets that feature files which are normally edited (Word docs, etc.) and omit files that normally aren't (MP3's, etc.), even though the term 'normally' even here is a stretch.
Thanks.