Hi to all,
I've opened case #5204793 and would like to post the same question here. More experience, more answers?
I'm testing right now a failback operation. Here our scenario:
3 VMware infrastructure
Infrastructure 1 (our own):
- VM Backup & Replication Server
This infrastructure holds only this server.
Infrastructure 2 (customer's Production Site):
- All source VMs
- VM Source Proxy
Infrastructure 3 (DR-Site on a different location):
- All destination VMs
- VM Target Proxy
Connection link: WAN 30MBit with layer2 managed by us.
Failover went well and fast.
In order to reduce the times of failback I've incremented our WAN network for our customer. 30MBit to 100MBit/s. Now, I'm noticing there is another job that it takes long time to complete:
"Calculating original signature Hard disk..."
Who is calculating this signature? Source proxy, destination proxy, B&R Server, ESX?
How is the network flow during this operation?
So, if I know who is doing these steps, in example the proxies, I could increase the vCPU in use and reduce this time.
Any help to speed up this task would be apreciated.
Additional quiestion. What does the follow means?
[ProxyDetector] Proxy [veeam-proxy-<snip>] lies in different subnet with host [VMware ESX 4.1.0 build-502767]
[ProxyDetector] Detecting hotadd access level
[ProxyDetector] Testing proxy ip [10.0.2.26], netmask [255.0.0.0]
[ProxyDetector] Testing host ip [188.8.131.52]
[ProxyDetector] Proxy [veeam-prox-<snip>] lies in different subnet with host [VMware ESX 4.1.0 build-502767]
[ProxyDetector] Wasn't able to find proxy vm but can failover to network
And it does failback to network...
The proxy is able to contact ESXi well. The host is seen on IP 184.108.40.206 only from the central B&R server. On the proxy it's contacted/resolved on the same subnet. This because the hostnames has different resolutions for nat settings and different network topology.
Thank's a lot!