Group: Forum Members
When Reflect evaluates the retention policy, the current backup is counted. This is mentioned in Reflect's documentation. So for example if you have a retention policy to keep 1 Full backup and you have "Run purge before backup" enabled, then every time you create a new Full, Reflect will delete all existing backups before it even starts creating the new one.
If that doesn't completely account for the outcome you saw, then posting the job log of the backup that behaved unexpectedly would likely be helpful. Make sure not to include your Reflect license key that's included at the bottom of the log.
If the issue is that you had a completely unexpected backup start immediately after you updated the schedule, I wonder if updating the schedule caused Reflect to believe that a bunch of backups had been missed since the start date and the current date. If so, that sounds like a bug. In that case, can you be as specific as possible in terms of what your schedule configuration was before you made any changes and what changes you made? And then are you using Windows Task Scheduler or Macrium Task Scheduler?