Does this make sense to you (design diagram)

[jbarrow.viracoribt]

Check this out. This is how I think my data is flowing right now. I could use another set of eyes. Does this look to make sense from a config perspective? The purple lines are fibre, the blue are ethernet.



URL since it looks to be getting cut off. http://i.imgur.com/KIJr8Z0.png

[kjc3303]

The Replication Job would be processed via the DR Veeam Proxy(I can only see the Physical One) which would write directly to the SAN

Data flow

Q: What is the data flow in case of replication?
A: Disk > Source proxy > Network > Target proxy > Disk

[veremin]

Your replication scenario does make sense in case of onsite replication. However, for offsite one it’s highly recommended to utilize two-proxy scheme. With proxy servers being set up on the both of the sides, the data will cross the WAN compressed and will be uncompressed by the target proxy.

As to your backup, you should be aware that LAN-free traffic flow will be guaranteed if only:

• Your Physical proxy server is connected via FC to both of the storages (Production, DR).
• LUN 61 has been mounted to proxy server.
• And proxy server is used as the target repository.

Hope this helps.
Thanks.

[jbarrow.viracoribt]

Thanks for the response!

For my backup jobs:

My backup Proxy at my DR sit does have access to both SAN's via FC. Pathways have been added to my FC switches to allow this.
LUN61 is mounted to this same proxy server as an RDM, it's showing up as Drive E:
The backup Proxy is configured as a target repository and its used for my backup jobs.

It does sound as if we're configured properly which is great.

[veremin]

It does sound as if we're configured properly which is great.

Yes, it really does.

Should any other questions arise, don’t hesitate to let us know.

Thanks.