What storage options did you specify for the container field(s)?
1 of 1 people found this helpful
-I configured the "additional database folder" and "additional container data" folder in the FMServer admin console to read data from our file server (a Qnap Raid 10 file server on the same internal network
QNAPs are NAS devices and NAS is a big no-no for a FM deployment and is not supported. I'm very surprised it even seems to work for the FM file. But I am not surprised that ultimately it just does not work.
There is probably nothing more essential to a stable FM deployment than rock solid disk i/o. By using a NAS device you are forcing FMS reads and writes through a network protocol and that makes it slower and more unreliable, thus brittle/fragile, even on a well designed wired network. The risk to file damage grows exponentially. Which is why FMI does not really support it.
Using the same 'remote storage' principle, but stepping up the hardware involved and you have a SAN. SANs are supported.
I have it set to "store container data externally", relative to the default container storage location, using "open storage" option using a particular subfolder for each container field.