When not using Azure Files or NetApp, consider the following for FSLogix Shares
FSLogix Profile Containers
FSLogix by Microsoft was designed to improve the virtual desktop user experience and simplify profile management for virtual desktop infrastructure (VDI). Keeping the VDI infrastructure and applications available and resilient to infrastructure problems is crucial for data availability and keeping businesses running. Administrators that deploy FSLogix profile and Office 365 containers need to provide high availability for FSLogix profile containers and all VHDs.
Combined with the following settings you can impliment HA on your FSLogix profiles where you aren’t using Azure Files:
HA Options for FSLogix
When developing a highly available solution, Microsoft customers consider two primary deployment options:
Option 1: Use FSLogix Cloud Cache
FSLogix Cloud Cache solves several conception issues. First, it provides a local copy of cached hot profile data of the container for the user profile, which reduces the network and CPU load of the file server. All read operations are performed locally, which significantly improves user experience in some cases. Using local cache also overcomes temporary outage of the infrastructure. All changes to profiles are stored locally first and then can be replicated to a profile storage location. You can specify several profile locations that will automatically create infrastructure highly available in an active-active configuration.
You need to provide enough storage capacity and performance (IOPS) for the cache.
Longer logon and logoff time due to a need to pre-load cache and flushing the cache back to the storage locations.
Depending on the size of your FSLogix profile containers and Office containers, doing so could translate into delays that could impact user performance.
Option 2: Leverage VHD locations and replicate data between these locations using other solutions
Using tools such as DFS-R, Robocopy, or Rsync, you may be able to deliver an active-passive high availability solution.
VHD/VHDX Replication Options
The Distributed File System Replication (DFS-R) service is an integrated Windows service that replicates data between data centers. DFS-R monitors changes to NTFS and replicates only changed blocks between Windows servers. DFS-R shows acceptable performance over the LAN. DFS-R is not the preferred solution if you want to replicate VHD files geographically across sites or to the cloud.
Robocopy is the file copy tool for Microsoft Windows. It provides basic, serialized copy operations between two locations. Because of its simplicity and wide availability, some people decide to use it for copying profile containers between storage devices. The obvious limitations of this approach are that you need to develop a set of scripts to make it robust (survive restart, report errors, etc.) to make it viable to work in the production environment.
Rsync is a well-known tool to effectively keep folders synchronized. It is very effective in detecting changes and making sure the folders are the same. It uses checksums to guarantee that files are identical after the transfer. While it is very effective in LAN, performance is significantly reduced over the WAN. You can’t use it to synchronize and replicate containers directly to blob storage in the cloud. You will also need additional scripts to make this work reliable in your production environment.