With WFF set-up, your sites get replicated/synchronized from primary node to secondary node(s), which includes both IIS site and web folder contents. However, the opposite doesn't work - nothing gets copied from secondary nodes to the primary node.
If the end user/client tries to connect and is automatically redirected to a secondary node, then whatever they upload will not be replicated to primary node or any other secondary node. In fact, it will disappear, because replication works only from primary node to the secondaries.
Taking that into consideration, what is the best practice for setting up FTP service on WFF???
Now if you're using NLB or ARR, you can set the load weight to 100% for your primary node and that will insure that end users always connect to the primary node, but that sort of defeats the purpose from load balancing point of view. So based on that I am wondering if there are any more graceful solutions out there.
Please share if you have any better ideas.
-znerses