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 ...[URGENT] Configuring DNN in a web farm with locally replicated files[URGENT] Configuring DNN in a web farm with locally replicated files
Previous
 
Next
New Post
1/11/2011 11:12 AM
 
I am running DNN on a test server right now. The user group just informed me that they want this moved to production soon. However, we are running a 2-server web farm in production and I don't think I have time to get a central file server established for DNN to attach to. The web farm is running Windows Server 2003 with IIS 6. I see people talking about using locally replicated files between the nodes in the farm, but no details on how to do that. What do you folks recommend? Is there something built in to DNN to replicate files back and forth, or do I need to set up a windows task or something else to do this? Thanks in advance for any assistance!
 
 
New Post
1/11/2011 1:15 PM
 
I actually have used this method a few times to avoid the single point of failure in a central file store.  Files stored on each web head is much more reliable. Each web head acts independently and a program, such as PeerSync, can be used to sync the websites file directory in real time.


 
New Post
1/11/2011 1:25 PM
 
Chris Smith wrote:
I actually have used this method a few times to avoid the single point of failure in a central file store.  Files stored on each web head is much more reliable. Each web head acts independently and a program, such as PeerSync, can be used to sync the websites file directory in real time.

 As it turns out, our company licenses a similar product. What settings do you recommend for this? Should the sync be set up to go immediately? Or every x minutes? What configuration settings do I need to be aware of in this setup? Will this magically work if I set up each node separately and then sync the files in the background? Thank you.

 
New Post
1/11/2011 3:51 PM
 
Yes, you should sync in real-time. You would'nt want to publish a blog with an image file and the image to not appear for on a server for X number of minutes.

How you set it up on the servers is a matter of need.  For instance, one client of mine only allows employees to upload files and images to the website, So an internal DNS rule is in place that pushes their website domain to the address  172.16.X.101. So 172.16.X.101 is the "master" for sync'ing to 102 and 103. If you're going to allow editing on all web heads, then you'll need to configure as such. Each Sync software is a little different, I know that PeerSync allows for a 'master' type approach, you'll have to check your software's documentation on sync'ing multiple file stores.


 
New Post
1/19/2011 2:34 PM
 
Thank you! I used our company's third-party file synchronizing software to sync the directories on each web server, and it seems to be working fine so far. All I had to do was clone the record in the dbo_PortalAlias table and point to the new machines.  ex: Changed http://myTestserver/PortalName to http://myProdServerA/PortalName, and added a NEW record for http://myProdServerB/PortalName.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...[URGENT] Configuring DNN in a web farm with locally replicated files[URGENT] Configuring DNN in a web farm with locally replicated files


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