I about to implement our DNN system to a laod balanced server farm. I have read the DNN server farm documentaion and am cool with the info and I think Ive configured the web.config file etc my main issues are whats not in the documentation.
As an example of the setup, The balancer resolves a domain name www.jim.com an the primary server resolves the name www.server1.com and the secondary (mirrored) server www.server2.com etc.... there is a seperate shared MSSQL server
ATM the balancer is pushing all requests to the secondary server, server2 and the server hasnt been mirrored....so the problem is how do I complete the instalation on a load balanced server, if it initialise the process on the secondary server it wont mirror back to the primary server or is the initialisation only a DB issue and no files are changed in the folders or web.config file???
If I directly access the primary, server1 will that cause an issue as the URL will be setup for the wrong URL?
or would the URL www.jim.com be a portal and the default portal will be the www.server1.com???
How is module installation handled in a server farm? for instance if I access the system via the porper URL www.jim.com and install a module, I could be installing it on the secondary server, server2 which means it will never end up on the primary server, server1 , is this where I need a shared file server? or do I need to do all module instalations directly to the primary server www.server1.com?
Also when adding content to the website where do the images and other resources get loaded into the system? is this where the shared file server come in?
What are the issues around the file replication service? the documentation it talks about heavy file changing activities, what considered and "heavy"
thank for any help offered