DDBoost Virtual Synthetic not for BCJ?

[filipsmeets]

Am I right to assume that DDBoost Virtual Synthetic does not work for Backup Copy Jobs?

As for some background, you can read the following post: veeam-backup-replication-f2/backup-copy ... 66800.html
Implementing Veeam WAN accelerators and a gateway at the target would probably work but would also require a serious investment for extra compute. So this is not something we can do right now.

[foggy]

Hi Filip, backup copy jobs also benefit from the virtual synthetics, unless the 'Read from source..." check box is enabled - in this case there's just no synthetics.

[filipsmeets]

Is this also true for GFS?

[foggy]

Yes, GFS restore point creation depends on that option - either it is done synthetically or the data is completely copied from the source repository.

[filipsmeets]

Is there any dependency on the proxy/gateway server during this process? As ours is at the source, would there be a lot traffic going back and forth over the WAN?

Really appreciate the fast answers here. Thx!

[foggy]

Yes, all communication with the storage is done via the gateway server. As I already mentioned in your original thread, having the gateway closer to the storage could improve the performance (or at least show the real bottleneck).

[filipsmeets]

We can confirm that using a gateway at the target location increased or transform operations x 5.
Runtimes for the backup copy itself stayed the same. It would've been nice if it was possible to define a gateway solely for the transform operation so we could keep using DDBoost over WAN.

Thx.

[foggy]

I'm noting your request, however, since you already have a gateway in the target location, are there any reasons to continue using DDBoost over WAN?

[filipsmeets]

Hi foggy
Yes. We use DDBoost over WAN to reduce the load on the network together with SilverPeak on SDWAN.

[foggy]

Got it, thanks.