I'm doing some research into how I can turn my relatively primative windows servers separate webservers into a more sophisticated load balanced server farm. We host hundreds of copies of our own ecommerce software, meaning there are many many files, but few changes on a day to day basis.
I'm ticked off some key areas in my research already, network load balancing plus some service monitoring controlling it, no problem. IIS metabase updates, no problem.
But I am stuck how to replicate the actual sites contents. As all the websites have client control, any updates, e.g. new images uploaded via their webinterface need to be very quickly replicated onto all webservers.
Solutions like robocopy are not fast enough for me ( I have 2.5 million files to replicate! ) even though there is hardly any changes ever happening. I suspect I'd get better resulted with something like rsync (or windows wrapped version) but I'm hesitant to write my scripts with that in case it doesn't scales to the full 2.5 million files well.
Another way is to serve the content off a single SAN/NAS. However I only have 10/100 nics to play with, and I'm worrying that the network will become a bottleneck with that.
I believe there are some commercial solutions out there too. (but are they any better than e.g. rsync?)
So it appears windows distributed file system with DFS replication seems a good bet to sync my content. However I fell over with this method as it requires a domain, and no, I don't have a domain in my network yet.
So my questions are these:
* I'd really like to avoid adding a couple of DCs to my environment just to get this to work, can anyone tell me whether this might be worth my while, e.g. is very easy or worth it?
* Any other way to get DFS replication working without a domain?
* Any other 3rd party equivilent for window DFS replication that can work in my enviroment?
* Any other tips suggestions to get me back on track?
I'm frustrated that I've got so far on my research, but fell on this hurdle.