seed copyjob from replica backup

[lowlander]

Hi,

we have two locations. Location A is replicating a VM on location A to a replica on location B. We also make a backup of the VM in location A and send it by means of a copy job to location B.

The copyjob left the building and has been deleted:) and now we have to create a new copy job, that copies the backup of the VM on location A.

Is it possible to make a backup from the replica VM on location B, and use this backup as a seed for the copy job that makes a copy from the backup on location A to B ?

thanks !

[foggy]

Yes, this is possible. Just map the new copy job to the backup created on site B and it will continue sending changes only.

[lowlander]

Thanks for the confirmation Foggy,

I assume that we need to place the backup on site B in the same backup repository that is being used as target for the backup copy ?

[DGrinev]

It's not mandatory to use the same repository, you can add any site B repository with backups in it, initiate rescan and map the new job. Thanks!

[lowlander]

Very clear, thanks !

Just wondering : Is it also possible to create a backup of the replica on site B, and refer to this backup. In the copy job it is possible to select source repository for the virtual machine by selecting the repository with the backup of the replica on site B. With this is it also possible to prevent data from transfering initially over the WAN link ?

[lowlander]

Unfortunately we replicate server01 on Site A to server01_replica on Site B. When we create a backup of this replica, and map it to a new copy job a new full backup is created and traffic is transferred over WAN. Any suggestions how to fix this ?

[lowlander]

Just to keep you informed...

Renaming the replica and performing a backup on site B also is not helping much. When mapping the backup and starting the copy job I noticed : server01 is no longer processed by this job. Make sure this change is intentional. After that the source repository on site A for the backup of server01 in Site A is being used.

Looks like it is impossible to use a backup from the replica vm as a seed for the initial copy job.

Any help would be appreciated

[foggy]

Right, sorry for confusion, seems I misunderstood your setup first. The replica VM has a different VM ID and will be treated by Veeam B&R as a different VM - while you can map backup copy job to this backup, entire source VM still needs to be transferred into a new incremental restore point. Once this restore point is merged into the full backup according to retention settings, corresponding blocks will be deduped. To avoid data transfer over WAN you need to physically send the backup file on some external media to the target location.

[lowlander]

NP, good we experienced that one Sounds to me like a feature request : using a replica from a virtual machine as a seed for a copy job in case the target repository fails.

thanks !

[foggy]

Noted.