Group: Forum Members
Ok, in that case I'm curious what happens at your next scheduled Incremental that's going to the same disk you used for the test. And to be clear, the decision to create a Full even when an Incremental is specified has nothing to do with the properties of the output/destination disk. Reflect doesn't even maintain a "memory" of other destination disks you might be using with the same job. It works with the destination that's available at any given time, without maintaining any sort of link between different destinations. If Reflect creates a Full when you ask for an Incremental, it's based purely on comparing the contents of existing backup files on the disk to the source data being backed up in the currently running job. A volume label change wouldn't cause new backups to no longer match existing backups, because I've changed volume labels on source partitions without that forcing me to create a new Full.
If you want to try to get to the bottom of this, post two different screenshots:
#1. The Restore tab in Reflect after selecting the last Incremental that was created before Reflect created an unexpected Full.
#2: The Restore tab in Reflect after selecting the Full that was created when you were expecting an Incremental.
When each of those backups is selected under the Restore tab, the partition layout of the disk(s) captured in that backup are shown above the list of available backups. I suspect that if you compare those, you will find some sort of difference in the source, either in partition(s) selected or their sizes.