Storage Optimization setting for Pull replication

[tim.vogel@xtium.com]

When setting up v5 replication (or backup) jobs being done remotely (Pull replication) across a WAN, what is the appropriate settings for inline data dedupe, compression level and storage optimze?

Example:

Veeam 5.0 enterprise installed at DR facility, connects to remote VC/ESXi hosts across the WAN and pulls VMs back to the DR site storing on SAN disk / ESXi hosts in the DR facility.

Looking to minimize time and traffic as much as possible.

Has v5.0 done anything to make push replication make more sense?

[Gostev]

Hi Tim, defaults are good, just change storage optimization to WAN target in the advanced job settings.
There were no architectural changes in v5 around replication, but we have some coming in the next release.

[tim.vogel@xtium.com]

So WAN target for the storage optimization means WAN between the source and the Veeam server, or between the source and the destination, or between the Veeam storage and storage?

[Gostev]

Between Veeam server and target site. This helps push replication by reducing traffic for incremental runs significantly. Just answered your last question but missed everything else...

With ESXi targets pull replication might still be better for now, until the next release.