Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN 6.2.6 CE web farm with multiple file serversDNN 6.2.6 CE web farm with multiple file servers
Previous
 
Next
New Post
8/1/2013 4:56 PM
 

Hi,

We are planning to convert our website which is running on single server to a web farm with two servers on Windows 2008 R2. I am afraid I haven't found lot of documentation on this topic. Can any one point me to the proper documentation for this. The one document I found is

http://www.datasprings.com/resources/...

This one explains using single UNC share as file server but we are looking into to use every server in the web farm as file server (i.e have dotnetnuke folder on all the server's local drive) since UNC share becomes single point of failure (I don't have big understanding on this topic, please correct me if my assumption is wrong about single point of failure).   So my questions are:

1. Can I do DNN web farm with multiple file servers, if so, how?

2. And also, how does the modules updates should be done? Does it need to be done on all the servers separately or does the DNN has any inbuilt mechanism for this or do we need to use DFS replication between the servers?

3. Also, we use heavy caching. Since we have to use file caching in the DNN CE web farms, how does the caching works with multiple file servers?

Also, please let me know any points or gotcha that I need be aware of. Any help is greatly appreciated.

Thanks,

Ana

 
New Post
8/12/2013 9:24 PM
 

1. yes, it's perfectly possible. The wiki has some useful information - http://www.dnnsoftware.com/wiki/Page/... . Basically we need a shared space where cache entries can be written so that things do not get stale. The filebased caching provider uses a UNC path as it's shared space - but that's all that needs shared. The caching providers do not take care of the files themselves, you have to manage that. The most common ways are to put them all on one machine and set all your webservers to access that via UNC, but it's equally valid to use other synchronisation approaches such as Microsofts DFS - we even have some users using simply programs such as robocopy.

2. install the module on any of the webservers - this will create some database entries (which is fine as all the webservers use the same database) and create the files on that machine. If using a UNC approach, then the sites all share the filesystem so nothing further needs done. If doing synchronisation, whatever approach (DFS, robocopy) they will automatically copy the files to the other machines.

3. that is what the cache provider is for - it synchronises the cache on the different machines e.g. if a site setting is changed on one machine, and stored in cache , the cache provider will create an item to handle the expiry of it. If you're using the file based provider it does this by creating a small file.


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/15/2013 3:56 AM
 

just a tip - if you have the option put the shared cache UNC on a raid drive or a ssd - it can get a serious pounding in a heavily loaded system - and can wind up being the bottleneck if performance is what you need.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN 6.2.6 CE web farm with multiple file serversDNN 6.2.6 CE web farm with multiple file servers


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out