Retention Policy not working? Old restore points still there

[MaccaNZ]

Anyone else come across something similar to this?

We recently changed our Backup job from the Incremental with the Enable Synthetic Fulls (Forever Incremental) enabled because we started to run low on storage space, so the job was changed to remove the Enable Synthetic Fulls (Forever Incremental) and just have the active full every Saturday. With a retention policy of 14 restore points which is working fine, we've had 2 full weeks of backups without any problems.

However the older Forever Incremental restore points haven't dropped off after changing the retention period and altering the job. They're still there, so now the next question is how to remove them safely (149 .vib files) I know that people have said you can delete them off the storage but the response to that seems mixed.

Any thoughts?

[foggy]

Chris, how many weekly active fulls have been performed after the job settings have changed? And files do you currently have in the repository folder except those 149 vib's?

[MaccaNZ]

...Come in the next morning do a quick refresh and they're all gone! the retention policy has taken effect and there's now only 14 restore points...

Thanks for the reply...

[veremin]

Chances are, there have been less than 14 restore points, counting from the latest (or previous) full backup. Therefore, retention setting could not take place. Thanks.