tsightler wrote:Based on your setup you can use the same server to talk Catalyst to the local StoreOnce to read the data, and talk Catalyst to the remote StoreOnce to write the data, so you're still technically talking Catalyst on both sides. Do this with per-VM and you get parallel BCJ with local Catalyst and Catalyst across the wire. Still not as efficient as Catalyst Copy, but can be quite workable in many situations.
Interesting architecture (Catalyst->LAN->Proxy->WAN->Catalyst) to "keep it talking Catalyst", but what if you have another proxy in play because you're also using the second StoreOnce for local backups (Catalyst->LAN->ProxyA->WAN->ProxyB->LAN->Catalyst)? Does Veeam recognize that the ultimate source & target are both StoreOnce Catalyst Stores and still "keep it talking Catalyst"? If so, does it still make sense to use WAN Accel for connections <100Mbps (when permitted by license & infrastructure)?
In my design, we have a StoreOnce in each of two locations for local backups, and we're doing copy jobs from each local to the respective remote StoreOnce. Small jobs have been working well, but bigger ones are...troublesome, especially when we also try to use WAN Acceleration to beef up the efficiency of the 20Mbps WAN.