We modified some scale out repos by adding some new extents and then evacuating and removing the old ones. We have about 100 Replication jobs that run after the backup jobs and there appears to be a bug. If I try to run the replica jobs again after the change to storage the job fails with:
3/22/2016 3:19:22 AM :: Error: Backup repository 'cbd01cdf-ad1a-4f56-a0a0-9325f719e221' was not found
If i simply edit the job, and press finish, it works again. Like it has to discover the storage location. How can we get around this? I don't want to have to open each job, it takes a bit for each one to resolve its settings.