FSLogix cloud cache proxy and cache locations on smb share

Copper Contributor

Dear colleagues, we are trying to create fault tolerance profile storage system with several places to store profiles

1)Hot on SSD (First Priority)

2)Cold on HDD (Last priority)

All RDSH VMs are running on NVMe full flash storage.

While enabling Cloud Cache Proxy and Cache folders are created and using space from drive C. In some cases this may consume up to 100G for cache per VM, also adding unneeded load for the NVMe storage.

We have been expected to use SMB share for at least cache storage, it also have low latency and good io.

But after entering SMB share as path - folder for profile created ok. But not profile. Process fails with such error.

SessionId: 2. FrxStatus: 31 (The create operation failed because the name contained at least one mount point which resolves to a volume to which the specified device object is not attached.)

mklink also have the same behaviour.

We also could create additional VHD and use another drive to redirect load to SSD but this looks like work around.

Could we some how place cache and proxy directly on SMB share (sofs)?

This happens starting from 8111 version and also tested on 2.9.8612

5 Replies
Hey Alex, we have Cloud cache enabled in environment, but I haven't seen that cache is growing up to 100GB, How many users generate so huge cache? just curious.
As I know you unable to redirect Cache and proxy to the file share, only local drive (we have separate drive for this purpose, not a system drive)
https://learn.microsoft.com/en-us/fslogix/concepts-fslogix-cloud-cache#local-cache
Hi, Dmitry. We have approx 400 users total on RDS and 35-40 per rdsh. Max profile size 30G, average is 4G.
In this case make sense, 35-40 users I guess can generate 100 GB of cachingm but in our case we have about 1GB of caching per user session and removing all cache and Proxy folders after logoff,
So what the problem except huge disk space because of caching?
this error during logon?
"SessionId: 2. FrxStatus: 31 (The create operation failed because the name contained at least one mount point which resolves to a volume to which the specified device object is not attached.)"

Do you see error on every logon?
do you use just SMB file shares for cloud cache? Can you share CCDLocation setting?
Have you tried to update FsLogix version to the latest?
We also expect to clean cache on log off. Problem is storage cost, cache will be saved on NVME storage and saving up to 1TB data is costly and no such performance needed. We expect to use full flash storage, that more than 2.5 times cheaper. Second reason is to receive high availability of with SOFS. All CCDLocation are SMB, graduated by performance. Seems like we have to use same work around with dedicated disk creating.