Launching CMS Orchard website behind a load balancer

I need to deploy an orchard application to a site that is in a web farm, behind a load balancer. It looks like it's going to be a fairly common scenario, but I can't find any guidance on how to make this work outside of Windows Azure.

The Orchard documentation describes how to deploy multiple instances to Windows Azure. He points out three issues that need to be addressed, but all solutions depend on Azure.

http://docs.orchardproject.net/Documentation/Deploying-Orchard-to-Windows-Azure

• Media files stored in the file system. There are also files stored in the App_Data folder for example. search indexes. Wouldn't that be a problem? What's the best approach to solving this? Running a site from a file share? Using Windows DFS to Replicate Changes? I would rather not use a file share
• Data dumping and database caching use local storage in conjunction with signals that are invalid to cache the cache only on the local server. Does the distributed events module solve this problem? https://orcharddistributedevents.codeplex.com/ Or maybe Orchard.Redis functions?
• Session state is stored in local memory. I am guessing I can enable sticky sessions in the load balancer or just use SQL Server for the session state.

I found an old post ( Orchard CMS on Load Balanced Web Servers , back to Orchard 1.1) that suggests setting the machine key setting in the web.config file.

I suspect I am having problems with the warm-up module? And I came across the Orchard.TaskLease module, which seems to imply that there is a problem with tasks running on multiple servers where they should only be running on one.

Has anyone successfully deployed Orchard in a load balanced, non-Azure environment? What modules and special configuration would you suggest doing this job?