We have two active sites one called HO acting as primary site and one called DR acting as Secondary Site. Every environment is different especially with VDI because of the tight integration of all IT components ( servers, storage, networking, security, virtualization, … ) required to establish a working VDI environment let alone an active or passive DR. I understand there are many different requirements in terms of DR and solutions to meet them, I am not trying to cover all scenarios but rather establish a baseline for us to build upon. Honestly speaking putting this setup into words is no easy task although when understood the logic behind it is fairly simple so I urge you if anything is not clear ( my bad ) just try to read it more than once while contemplating the diagram below until everything makes sense or drop me a comment/email and we can take it from there. Both sets of users should have the same Profile/Data needless to say. Users in HO should be able to failover to DR in case of disaster and vice-versa users in DR should be able to failover to HO incase of disaster. We have a Primary Site ( Head Office ) with users local to that site and a Secondary Site (Disaster Recovery) with users local to that site. In this post we are going to take a different scenario and approach. Well it applies to a certain extent but configuration would surely differ, one that comes to mind is that in a stretched site deployment we will have to use the DFS namespace in UEM or GP rather than the independent replicated share cluster name path in each site. The reason I say WAN link is that a stretched site or sites connected using dark fiber are not considered as a multi site deployment so whatever has been discussed does not apply. VMware Horizon 7 Multi-Site with Microsoft Azure GSLB Traffic Manager
VMware Horizon 7 VDI Active-Active/Passive Multi-Site Disaster Recovery Part 1 In part 1 of this series we discussed a seamless active-active VMware Horizon View deployment in which HO & DR sites where connected over a WAN link and users are able to connect to either sites internally/externally using the same profile and data.
0 kommentar(er)
