I am looking at moving my Veeam backups to a new Windows 2016 repository server that I have created. I have a few barriers to a straight migration (copy the existing files to the new repository and get the benefit from new backups after a full).
The barrier is that the current repository is using duplication and the backup target I am using doesn't have enough free space to hydrate the backup onto a ReFS datastore (no block magic until it actually runs the next full). This means I need to transition from the current repository to the new one.
To me, the best way of achieving that would be to use Scale-out repositories (my target is already scale out as with deduplication I was using one repository for fulls with with deduplication enabled and another for incremental without deduplication). I just add my new ReFS repository to the Scale-out group, change policy to "Data locality".
The problem now is, how do I get it to stop using the old repositories for new data? I am guess that when free space on the new repository is below what is available on the old ones it will start to place data there. Once all the configured recovery points are on the new repository I want to retire the old ones, but I need to get there first.
Any suggestions? I have thought about leaving them in maintenance mode, but I have other members of the business who need to be able to recover (needs repository online). I thought about creating a dummy proxy with no backups assigned and changing the old repositories to have an affinity to that.
If there is a better way, please share.