Win 2003 FailSafe Setup 1

[esabet]

Hello All;

I work for a Medium sized business and they are currently running a Windows 2003 Server R2 Enterprise edition. The Server is currentky being utilized to host a Web-Based Aplication, run SQL Server 2000 and Terminal Server.

With that in mind they have asked me to setup a fail-safe environment. The idea is if the server goes down due to a hardware/software failure then a second server will take over so there is minimal down time giving them time to fix the failed server.

I have some minor understanding but was not sure where to begin really. Any kind of resource or infomration that specifically focuses on such setup will be greatly appreciated.

Alternative solutions are welcomed!

 

[58sniper]

split those roles apart. load balance the web server, cluster the SQL server. TS and SQL are both resource intensive, so I'd never put them on the same box.

you could also look into NeverFail and DoubleTake, both of which provide some failover options

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[esabet]

Thank you Sniper. I checked out the websites for both NeverFail and DoubleTake and they look to be prefect solutions. Have you ever come across them or have you used them in the past? Any pros and/or cons?

Thanks.

 

[58sniper]

We're a NeverFail partner, and we do have some clients that use DoubleTake.

Check out DoubleTake - they usually have weekly webcasts that show their products in action. Pretty slick.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[technome]

Used Doubletake, works great.. at the time of last install it was the least CPU intensive of a number of "replication" packages, which is very important. Which ever you use, most allow full enabled demos for a specific time. As with any packages I tried, I setup the system NOT to do automatic failover, but a manual failover. Automatic creates problems if you need to reboot the main server for patching, testing etc. The manual failover requires a few minutes to bring up the "backup" server. As with most packages it works best with a dedicated NIC for the link between the main server and backup server. Do not even try CA software's package, it sucks, as does the support. Most packages are easy to setup, but tread lightly when tired or stressed, mistakes can be made, as in replicating in the wrong direction...fully understand the package before making replication choices. Sunbelt Software for a discounted price
Good Luck

........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm