When this happens, the new backups are no longer considered a "matching" relative to the old ones because the partition layout and/or selection has changed - and consequently, as described in that KB article, the retention policy would not apply to the old sets, nor would the disk space threshold rule. You may find a note to that effect for the Full backup that ran on. Otherwise, did you extend/shrink any partitions included in your backup or change the selection of partitions/disks included in the backup between those two backups? Reflect only creates Diff/Incs on an existing set if the partitions in that set are an exact match to what is being backed up currently, otherwise it creates a Full even if a Diff/Inc was requested and notes this deviation in the log for that job. You can change this to "All sets in the destination folder", but if you do that, make sure you only have a single backup job from a single PC storing backups there, otherwise the retention policy for Job A would be allowed to delete backups created by Job B.Īs for why Reflect created a second set of backups, assuming the answer isn't that you requested a new Full, did you upgrade to a new release of Windows 10 between 12/16 and 1/27? If so, the behavior described in this thread probably occurred. You of course have two sets there, but it's possible that the old set isn't considered a "matching set" (more on that in a moment) and the default retention policy is to apply it only to matching sets. the latest Full and its child backups) is never evaluated for deletion, so if there's only one set, then nothing can be deleted by that disk space threshold rule. A set is defined as a Full and all of its child backups. The free space threshold deletes older backup sets, not older backups.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |