Hey John,

I recently asked the same question. Joe responded here   

As a follow up. I'm thinking about how to do this without changes to the code. I'm moving my site to a cloud based platform and am going to use a centralized storage device. I'll point the data directory to this device so that all web servers will have the same data directory. Everything else will be replicated across the web servers.

Not sure what issues I'll run into but I'll try and post results in the other thread once I give it a try.

Well, for starters you will have to adjust the logging.

Currently mojo writes the logs to the Data folder and they're named:

currentlog.config, currentlog.config.1 and so on. Each server would therefore attempt to log to the same filename and despite the robustness of log4net, there are some shortcomings.

Good point. I think we'll have to update the logging to allow for a custom log file name in the web.config. That way, each web server could have it's own distinct log file. We would want that anyway for troubleshooting.

Let's keep this thread going and post all the issues we see, that way, when someone starts to tackle this we'll have a big head start.

That's encouraging. So if two servers have a virtual Data folder to a common shared disk space and each server's log file is given a distinct name in the log4net.config file, are there any other gotchas? Or should this be the workable solution?

Thanks again

Will do.