I'm afraid that I'm not following you on that. If you utilize proxy A to backup site B then the traffic will go between sites from ESX-A to Proxy-B right through those switches, won't it? By the way, where is your backup repository located and how is it connected to proxies?The idea behind this rather unusual approach: Between these two sites are several switches we don´t want to burden with the load.
May I ask you what ESXi version are you using? Please check this VMware KBThis approach turned out to be more problematic as we thought, as when a VM uses vMotion, another backup job now is responsible and its causing a new full backup of the VM.
That's not quite correct. during backup job proxy retrieves data from ESXi host via network/hot-add/direct-san and then sends it to the repository. Backup server just orchestrates the process unless you use it as a proxy. Have you considered using direct SAN approach to make backups locally and then ship copies from site A to site B and vice-versa using Backup Copy Job?So we thought, thate the proxy queries the data of the ESXi servers on his site and sends the data directly via crosslink to the other backup server.
Users browsing this forum: tdewin and 1 guest