I’m trying to design high availability for FSLogix profile containers and folder redirection in a small on‑prem environment. I’d like to mirror the “Multiple SMB Locations with Single VHD Path and DFS” approach described in this article by James Kindon: https://jkindon.com/architecting-for-fslogix-containers-high-availability/ Is anyone doing something similar? If so, what are you using to replicate the FSLogix containers and redirected folders between SMB locations (DFS‑R, storage replication, third‑party tools, etc.)? In particular, does anyone have experience using Dell RecoverPoint to replicate FSLogix containers and/or folder redirection data to a secondary site? How has it worked out for you in terms of performance, consistency, and failover/failback?

An important note that I don't see is that DFS-R should not be used, as it can lead to profile container corruption. DFS-N is supported, but not DFS-R for replication. It shouldn't be considered an option at all.

oh wow..thanks for the information..i didn't know that.

No prob. FSLogix used to have a dedicated page on it which I can't find anymore, but I'm 99.999% sure it's still the case. I've personally seen it when an org used, and it didn't take more than a a week for major problems lol.

yeah, i can't find it either..

I could be wrong, but I think those Microsoft clustered file servers were supported, but I've never seen one setup from scratch.

I don't think they will want to use DFS-R anyway..

DFS-R is the devil

I use bvckup2 works great. I have a DFS-N namespace \\corp.com\fslogix with a folder called profiles and then two DFS targets to two seperate CIFS shares on the netapps in each datacenter. The DR DFS folder target is disabled. I replicate the containers OOH with bvckup2 and exclude the ODFC containers