V8, Replication from Backup with DDBoost

[Baptiste]

Hello everybody,

Here is my case id : 00681452
I am running with two Datadomain and i am glad that VEEAM V8 use DDBoost . But i am facing an issue with Replication From backup :

i have my backup on my datadomain01 with DDBoost.
I use replication between datadomain01 and datadomain02.
I added on VEEAM the repository from datadomain02 and i can see my backup under disk (imported).

Now when i am trying to start VEEAM replication job from source : backup on datadomain02 it fails with: No restore points found

Am i doing it wrong ?
Before v8 and without DDBoost i could use replica seeding in this configuration.

Thanks for your help

[foggy]

Replication cannot be performed from imported backup, unless some backup job is mapped to this backup (otherwise it would be a one-time operation, just like seeding).

[Baptiste]

Thanks for your reply,

I have created a dummy job to map my offsite backup.
Now my replication job doesn't fail and wait in : Resource not ready: Backup repository

Will keep you update.

[foggy]

Well, since you're using storage replication, the backup chain is changed "outside" Veeam B&R and backup repository should be re-scanned each time so that replication job could "see" the new increment.

[Baptiste]

Alright, replication worked from my "replicated backup offsite" with a dummy job

i'll exec a PS script to update my repository before the job !

[veremin]

In version 8 we've added new commandlet using which you can rescan VB&R entities:

Code: Select all

$Repository = Get-VBRBackupRepository -Name "Name of your backup repository"
Rescan-VBREntity -Entity $Repository

Just specify this code as pre-job script.

Thanks.

[Gostev]

i'll exec a PS script to update my repository before the job !

Remember that in v8, you can use pre-job script to do this.

[tommyv]

Hi there, I'd like to resurrect this post if I may.

I am running a similar setup and have imported my backup repository. I have successfully mapped the backup sets to a dummy job and it can see all of the restore points. When I set up the replication job with the "source" set to the backup repository, its just fails with "No restore points found". Anyone have a smart idea of where I can look next to troubleshoot as it looks in order?
Thanks

[foggy]

Is there a chance that corresponding VM ID has changed since the backup was taken?

[tommyv]

Hi Foggy, The VM ID definitely hasn't changed, these machines are pretty static.

Whats odd is that the dummy backup job sees all of its object and all of its restore points so I'm not sure why the replication job cant see them.

[foggy]

Tom, you'd better contact technical support and let them verify your configuration. That said, please note that the dummy job approach is not a supported configuration but rather a workaround.

[tommyv]

Hi Foggy, technical support took a look at this with me but as you had a suggested, with this not being a supported configuration they were only able to go so far with it. We couldn't get it working in the end so I'm going to have to use another method.

[foggy]

I wonder whether support was able to identify the reason for this, as this was a viable workaround for some other customers previously.

[tommyv]

Igor from Veeam is going to run it in his lab so I will update if I hear any more.

[foggy]

Thanks! That would be valuable for future readers.

[jim3cantos]

In version 8 we've added new commandlet using which you can rescan VB&R entities:

Code: Select all

$Repository = Get-VBRBackupRepository -Name "Name of your backup repository"
Rescan-VBREntity -Entity $Repository -Wait

Just specify this code as pre-job script.

Thanks.

In version 9.5 update 2 we have had to add -Wait option to wait for the rescanning command to finish before continuing with the replication job. Without the option, we usually ended replicating the next to last restore point from the backup.

[spgsit5upport]

How does one create the dummy job to map the repository?

By default on DR site Veeam server I only get error:

"Restore point is located in backup file that is not mapped to any backup job "

Seb

[foggy]

You just create a backup job with the corresponding VMs and without a schedule and map it to existing backups at the Storage step of the job wizard.

[jim3cantos]

Ok, so after creating a new "dummy" backup job for a new repository at DR site and struggling for a while unable to map the backup from PROD site (no backups were shown in the repository), I was running out of options and ready to open a support case when I discovered that "It is not possible to map a backup job to a backup copy job chain since (v9) U3". I have just tested with a "dummy" (and disabled) backup copy job without problems.

[foggy]

Thanks, José, yes, this is correct, currently, you can map the chains produced by the jobs of the same type only.