Skip to main content
Solved

Scale-out Repositories Error

  • Oct 26, 2022 7:27 AM UTC
  • 8 comments
  • 888 views

Forum|alt.badge.img

Unable to add extent Local Repository because it servers as the target for one or more job types which are not supported by a scale-out backup repository.

 

We trying to add a new scale-out repository.

Best answer by MicoolPaul

In which case create another folder on the same repository server for your config backups, configure your config backups job to save to that repo, and then you can add your original repo to the SOBR

View original

8 comments

mkevenaar
Forum|alt.badge.img+16
  • Veeam Vanguard
  • Oct 26, 2022 7:28 AM UTC

Do you have configuration backups enabled and does that store the data on “Local Repository”? Or do you have any jobs currently that targets that repo?


Forum|alt.badge.img
  • Author
  • Comes here often
  • Oct 26, 2022 7:30 AM UTC

Hi MKevenaar,

Yes we do have the configuration backups enabled


mkevenaar
Forum|alt.badge.img+16
  • Veeam Vanguard
  • Oct 26, 2022 7:31 AM UTC

Hi MKevenaar,

Yes we do have the configuration backups enabled

Does the Configuration Backup target the “Local Repository”? You cannot add a repository to a SOBR when it's used by a job or the configuration backup


MicoolPaul
Forum|alt.badge.img+23
  • Answer
  • Oct 26, 2022 7:31 AM UTC

In which case create another folder on the same repository server for your config backups, configure your config backups job to save to that repo, and then you can add your original repo to the SOBR


MicoolPaul
Forum|alt.badge.img+23

Here’s the list of unsupported job types for a SOBR so you can further identify if you’ve got another workload that is unsupported in SOBR:

https://helpcenter.veeam.com/docs/backup/vsphere/limitations-for-sobr.html?ver=110


Chris.Childerhose
Forum|alt.badge.img+23

As noted here you can see what the SOBR cannot be used for like everyone has said above - Limitations for Scale-Out Backup Repositories - User Guide for VMware vSphere (veeam.com)


Forum|alt.badge.img
  • Author
  • Comes here often
  • Oct 27, 2022 6:47 AM UTC

Good morning All,

The issue has been resolved, as advised by @MicoolPaul we implemented his solution and the error was fixed. :) :)


MicoolPaul
Forum|alt.badge.img+23

Good morning All,

The issue has been resolved, as advised by @MicoolPaul we implemented his solution and the error was fixed. :) :)

Glad to hear all was sorted 👍