Resolution Summary

To resolve this issue, you'll need to first identify which jobs are still using the  option "Transform previous backup chains into rollbacks." This can be done either:

• manually, by checking each job's settings.
  
  or
• using PowerShell to pull a list of jobs that are using that setting.

Once you have identified which jobs are still using the setting, you'll need to either:

• manually reconfigure the job(s) to change to a retention method that does not use "Transform previous backup chains into rollbacks."
  
  or
• use the provided PowerShell scripts to switch all jobs that are using "Transform previous backup chains into rollbacks" to one of the two alternate retention methods.

Part 2: Reconfigure The Jobs

Once you have identified which jobs need to be modified, you'll need to consider which retention method will fit your space and retention needs.

• Switch to Synthetic Fulls only by disabling "Transform previous backup chains into rollbacks." This will cause the job to periodically create Synthetic Fulls, increasing repository storage usage due to how the Forward Incremental retention policy operates.
  
  or
• Switch to Forever Forward Incremental by disabling "Create synthetic full backups periodically," which will also disable "Transform previous backup chains into rollbacks." Using Forever Forward Incremental will maintain the same space usage as "Transform previous backup chains into rollbacks" but using a different retention method.