Hello,
there are any limitation using CDP replication with vCenter on Linked Mode?
We are trying to do Disaster Recovery test and we have a lot of trouble.
We are simulating production site down so primary vCenter is not accessible.
When we try to do a failover plan, it fails with a lot of errors:
- no replica found
- Failed to log in to vcenter, proxy srv: port:0 Cannot complete login due to an incorrect user name or password.
Even vCenter rescan fail with same error.
We think the problem was on how Veeam communicate with remaining vCenter (in DR site).
Due to Linked Mode, DR vCenter is very slow at logon (known behavior, aspected from Broadcom kb:
https://knowledge.broadcom.com/external ... ne-or.html ).
We also applied MaxVimSoapOperationTimeout registry key for increansing vCenter API timeout, with no result.
(https://knowledge.broadcom.com/external ... to-co.html)
In my opinion our configuration is common for VMware customers that have a DR site: 2 vCenter on linked mode.
During a real disaster the vcenter on the production site is not reachable and the remaining vCenter suffers this problem.
We have also have a lot of VMs replicated by SRM and VMware works fine also in this state.
With Veeam we can't activate the VMs. This scenario it was tested in Veeam Labs? (Vcenter on linked mode, with one vcenter not available).
Case ID: 07850787
-
- Novice
- Posts: 8
- Liked: 3 times
- Joined: Sep 17, 2021 7:09 am
- Full Name: Simone
- Contact:
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 13 guests