We have an Active/Active multi-site configuration, for DFS-N replication, is HUB and Spoke the only supported configuration or can one use full mesh?
Hi @mcity,
Given that you're talking about replication, I guess you mean DFS-R? And is this about DEM configuration shares or profile archive shares?
Yes it about DEM configuration shares or profile archive shares.
The KB below shows only DFS-N is supported
I meant DEM configuration shares
DFS-N (Namespaces) can be used for both the configuration share and the profile archive share.
DFS-R (Replication) can only be used for the configuration share, and – if used – must be configured in hub and spoke topology.
If I use DFS-N (Namespaces) for both the configuration share and the profile archive share, then I have to rely on the backend storage to do the replication. Correct?
If I use DFS-N (Namespaces) for both the configuration share and the profile archive share, then I have to rely on the backend storage to do the replication. Correct?
I assume so, but I don't have IT/deployment expertise. Hopefully one of the other forum users can provide some insight here.
Am asking as we have our backend storage replicates between the two sites, hence DFS-N should be the way we go. Lastly, is DFS-N full mesh topology is supported by VMware? there is not much information out there..
our customer has both DFS-N and DFS-R configured for profiles and config share between two sites. the key is to have individual share targets at each location as dem profiles do not fully support DFS-R
example:
DFS-N= domain name\userdata\dem\dem_profile
DFS-R= site one>> ServerFS01=active target, ServerFS02
DFS-R= site two>> ServerFS03=active target, ServerFS04
Thanks @zhornsby221
I am trying to avoid DFS-R as it's not fully or supported by VMware, hence I would like to use NetApp backend storage replication.
How is this configured so that DEM user settings is only writeable on one file server while the other one is read only?
I am looking at the link below, which mean I have to us Hub and Spoke.
https://techzone.vmware.com/resource/dynamic-environment-manager-architecture#configuration-share
I am thinking of implementing Centralized configuration share, so that changes to the configuration share are made to a primary copy, which is then replicated to the two sites using DFS-R.
Only draw back is that the namespace is active on one site and has to be failed over manually in case of an outage
Resilio Connect offers full mesh and/or bidirectional sync for active-active HA using VMware Horizon and DFS. You would use Connect instead of DFSR for the DFS namespace. See https://marketplace.cloud.vmware.com/services/details/resilio-connect-1?slug=true and https://www.resilio.com/usecases/vdi-synchronization/
Besides active/active HA, you should also see improved login times for virtual desktop users, especially in multi-site configs.