Hi,
Im preparing a DR strategy for our customer but would need help to better understand where Im wrong.
We have vmware with vsan on DataCenter#1 and another vmware with vsan on DataCenter#2 - Im doing replication from DC#1->DC#2
VBR01 located in DC#1 is also the source proxy and has vlanA (route added to windows for vlan B)
I deployed a VM as target proxy in DC#2 and this VM has vlanB as vlanA(bkp vlan is not present in DR#2) (route added to windows for vlan A)
Replication job for a test VM from DC#1->DC#2 is working fine with hotadd on both sides (in the job I selected: source proxy - VMware Backup Proxy|target proxy: DC#2VM)
Using source proxy VMware Backup Proxy for disk Hard disk 1 [hotadd]
Using target proxy DR#2VM for disk Hard disk 1 [hotadd]
I did a test and did failover now so I simulated that DR#1 has a problem and VM is running in DC#2, this is ok, but after I want do to a failback to production (migrate changes done on the VM DC#2 site to the original DC#1 site) I have the problem that for source proxy its NBD and its slow
No available proxies are running on ESXi management interface subnet. Using proxies from a different subnet, performance may be impacted
Using target proxy VMware Backup Proxy [hotadd]
Using source proxy VMware Backup Proxy [nbd]
****
Calculating original signature Hard disk 1 (60 GB) 1min.53sec
Replicating snapshot disk Hard disk 1 (60 GB) 66% at 30 MB/s - 22min.18sec still ongoing
Do you know what Im missing, what do to that for the failback it will do hotadd also on source proxy? For the failback operation Veeam is using only one vmware proxy for target and also source?
Thank you!
Im preparing a DR strategy for our customer but would need help to better understand where Im wrong.
We have vmware with vsan on DataCenter#1 and another vmware with vsan on DataCenter#2 - Im doing replication from DC#1->DC#2
VBR01 located in DC#1 is also the source proxy and has vlanA (route added to windows for vlan B)
I deployed a VM as target proxy in DC#2 and this VM has vlanB as vlanA(bkp vlan is not present in DR#2) (route added to windows for vlan A)
Replication job for a test VM from DC#1->DC#2 is working fine with hotadd on both sides (in the job I selected: source proxy - VMware Backup Proxy|target proxy: DC#2VM)
Using source proxy VMware Backup Proxy for disk Hard disk 1 [hotadd]
Using target proxy DR#2VM for disk Hard disk 1 [hotadd]
I did a test and did failover now so I simulated that DR#1 has a problem and VM is running in DC#2, this is ok, but after I want do to a failback to production (migrate changes done on the VM DC#2 site to the original DC#1 site) I have the problem that for source proxy its NBD and its slow
No available proxies are running on ESXi management interface subnet. Using proxies from a different subnet, performance may be impacted
Using target proxy VMware Backup Proxy [hotadd]
Using source proxy VMware Backup Proxy [nbd]
****
Calculating original signature Hard disk 1 (60 GB) 1min.53sec
Replicating snapshot disk Hard disk 1 (60 GB) 66% at 30 MB/s - 22min.18sec still ongoing
Do you know what Im missing, what do to that for the failback it will do hotadd also on source proxy? For the failback operation Veeam is using only one vmware proxy for target and also source?
Thank you!
Statistics: Posted by StanoSedliak — Oct 08, 2024 7:55 am