Fail over scenario

Yeah but the problem is that the files need to be real time synchronized,
since nlb is acting as a load balancer

I think the best solution is to have a fileserver behind those 2 webservers
where the webservers get their files from

Since this will be my single point of failure, im thinking to use linux as
fileserver

"Jeff Cochran" <jcochran.nospam.DeleteThis@naplesgov.com> wrote in message
news:4038f420.156099679@msnews.microsoft.com...
 > On Fri, 13 Feb 2004 11:36:01 +0100, "Mustang" <mustang.DeleteThis@mordamus.nl>
 > wrote:
 >
  > >I got 2 webservers running windows 2003 web edition
  > >Im gonna use them in a load balancing system
  > >
  > >This means when the 1th webserver goes down, the second down takes over
his
  > >IP adress, and with that all traffic
  > >
  > >This is working perfect, the only problem i got is the synchozing of the
  > >files
  > >
  > >I understood that can be worked out by dfs (distributed file system)
  > >
  > >But since i got the web edition, i can replicate with that, it needs a
  > >domain for that
  > >
  > >How can i still use dfs to synchronize files between the webservers, so
both
  > >got a updated version of the websites
  > >or is it better to work with scripts that copy files all the time
 >
 > It's better with clustering, which can't be done on the web edition
 > either. The most common solution is a scheduled replication using
 > Robocopy or similar, or a replication at the time the files are
 > transferred from the development server to the production servers.
 >
 > Jeff<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Fail over scenario 

On Fri, 13 Feb 2004 11:36:01 +0100, "Mustang" <mustang DeleteThis @mordamus.nl>
wrote:

 >Hi,
 >
 >I got 2 webservers running windows 2003 web edition
 >Im gonna use them in a load balancing system
 >
 >This means when the 1th webserver goes down, the second down takes over his
 >IP adress, and with that all traffic
 >
 >This is working perfect, the only problem i got is the synchozing of the
 >files
 >
 >I understood that can be worked out by dfs (distributed file system)
 >
 >But since i got the web edition, i can replicate with that, it needs a
 >domain for that
 >
 >How can i still use dfs to synchronize files between the webservers, so both
 >got a updated version of the websites
 >or is it better to work with scripts that copy files all the time
 >
 >Thanks for replying,

I use two servers as well. But I don't get complex with load
balancing. I image the hd from the first server to the backup server
(bus) and start that way. Then I use peersync mirroring software to
mirror the web, ftp and other important files to the bus. I export a
few registry entries to send to the bus as well like the odbc and
imail (mail server entries) and I import these into the bus.

I also use a program that sets up IP profiles on the bus so I can set
the IPs in the bux in the event of a failure. This configuration has
worked for me for 5 years.

For some reason I don't trust (maybe I just don't know how to use load
balancing) load balancing it all seems so complex - but then again it
may just be my simple nature.

Anyway, just a little more info for you to ponder.

John Cesta

---------------------------------
The CPU Checker - Maximize Server Uptime
LogFileManager - The only IIS Logfile Management Tool
DomainReportIt PRO - Helps Convert IIS Installs
<a style='text-decoration: underline;' href="http://www.serverautomationtools.com" target="_blank">http://www.serverautomationtools.com</a>


 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Fail over scenario 

MS has a tool available for everyone to uses to deploy to NLB cluster or from dev >> Stager >> Live cluster. Suggest that you have a look at this.

Application Centre 2000

Fanatasic tool, also provides health monitoring!!!
Have fun
 >> Stay informed about: Fail over scenario