Use SOBR as source for initial seed

[FrancWest]

Hi,

Case #04497182. We are unable to add our primary repository as an extent to a newly to create scale-out repository. The error we are receiving is that there are replica jobs using the regular repo. Before being able to add it, it seems I must disable initial seeding for al the replica jobs that use the primary repository (we are using seeding from backups). However, you can use the SOBR as a source for replication jobs when replicating from backups.

Why this limitation? What's the difference between a full seed and incremental replication? It uses the same backup files.

Also, because of this limitation we have to create workarounds for newly added VMs that also must be replicated since we cannot use the local storage of our Veeam server anymore for the initial seed since it has been added to the SOBR.

[Gostev]

we cannot use the local storage of our Veeam server anymore for the initial seed since it has been added to the SOBR

Why not? You can always create another repository on the same volume of your local storage, just in a different folder. It does not matter that there's also a SOBR extent using the same volume.

[FrancWest]

Yes, I know that, but I mean that our backups are stored then in the SOBR and I cannot use that for seeding.

[Gostev]

You can use backups stored in SOBR for seeding just fine.

To sum up:
1. Change your replica jobs to use a regular repository for replica metadata (create the new simple repo for this purpose).
2. Now UI will allow you to convert your primary repo into SOBR.
3. Use the SOBR as a data source for replication jobs.
...
4. Profit!!

[FrancWest]

Well, I just tried it by creating a new test SOBR. However, after creating it, it’s not listed in the drop down under ‘initial seeding’ on the seeding tab, but it is listed in the Window when clicking on ‘source’ on the virtual machines tab. So yes, I can use it as a source, but not for the initial seed. That’s the point I’m trying to make.

[Gostev]

That is strange... looks like some bug.

[FrancWest]

After looking at the case notes again, the engineer mentioned this page:

https://helpcenter.veeam.com/docs/backu ... ml?ver=100

In here it states:

IMPORTANT!
You cannot use a backup located in the scale-out backup repository as a seed for a replication job.

So, is this a bug or intentional and if so, why this limitation?

[Gostev]

We will need to investigate this, as it makes zero sense. Because all that is required to use backup as the initial seed for a replication job, is to read it... and we certainly are able to read backups from SOBR, because there are over 9000 other features which do exactly that! For example, full VM restore functionality does this, creating the same exact VM as replica seeding from backup would.

@Egor Yakovlev could you please investigate why does UI not allow this?

[FrancWest]

Thanks! That’s my point exactly. Please, keep me posted.

[Egor Yakovlev]

Hi Franc,

I have confirmed your case in the labs and checked with R&D - it appears that feature "Seeding from Scale-Out Backup Repository" was simply missed out from previous releases due to the low priority of the request, and has no visible technical limitations not to be included in the future builds. A fact that one can use Scale-Out Backup Repository as a source of Replication Job, but cannot use it as a Seed at the same time does not make much sense.

I will raise this topic internally and see if it's possible to add it for one of the upcoming updates.

/Thanks!

[FrancWest]

Hi Egor,

ok, thanks!

[theviking84]

Veeam v11 still does not allow you to choose a sobr repo as a replica seed repository. Is there any workaround for this?

[Egor Yakovlev]

That improvement is on track, but did not fit into v11, unfortunately.
As a workaround you can use Export Backup for said machine, and put it on non-SOBR repository to use as an initial seed.
/Thanks!

[dloseke]

Please add myself as another person requesting this functionality as I have at least one client needing to utilize a SOBR as a source for a replica seed. Any chance it'll be in the v12 track? Thanks!

[Egor Yakovlev]

Hi Derek,

Improvement is logged and works to be done, however there is no clear ETA yet.
Subscribe to this thread to be up to date with the status.

/Thanks!

[frankive]

Hi.
At most customers we have one SOBR repository with 1 local performance extent and 1 object storage.

If we try to create a replication job and use the SOBR (in practice the performance extent) as local seed to the new target host, the SOBR is not an option..

Why is that?

[Mildur]

Hi Frank

Please see the comments above.
Currently it‘s not possible.