Repo removal breaks all replication

[Strecker25]

I believe this to be a bug, but maybe there's a quick way around it? I removed 4 old repositories that were no longer used. As a result, all of our replication jobs failed saying they cannot find the repo's. THis is because we select "all available" when we build replcation from backup jobs. I have to open each job, open the backup repository tab, and then close. The job will then run properly.

I would think when a repo is removed it should be removed from all jobs as well, right?

Is there a quicker way to fix this issue, we have 100+ replication jobs that I now have to fix.

[Shestakov]

Hello Ryan,
replication jobs use repositories to store replica metadata, by default it`s stored on the default repository of that VBR server.
Removal of the repository should cause recreation of the metadata without any problems.
I agree that there should be a better way in the situation you`ve faced. Could you provide your product version?

[Strecker25]

Sure thing, we're on 9.5

[Shestakov]

thanks, Ryan.
Bug has been confirmed by our QA team and will be fixed in next product versions

[Strecker25]

Great, thanks.

So for now just the way we've been doing it is ok? Open the job, open repositories tab, close job. I just don't want to be doing any damage on the DB until the bug is fixed.

[Shestakov]

Your workaround will not damage the database.
You may also try to leverage powershell script to update all the jobs automatically.
Thanks!