Although a true geographically distributed solution would cost a lot of money, you should be shooting for a cost effective solution at a single NOC. You have to pick a NOC which you trust to have a reasonable uptime, and then set up your servers in such a way as to eliminate the single point of failure.
I highly recommend that you don't make your DB server that single point of failure. You should be using something like DFS or something similar to replicate the files from one server to another. File access should always be local; otherwise you will start running into issues. Hopefully, your client will grow, and they will be able to afford a second failover DB server and a second license of SQL 2005 Standard. At that point you will just need to set up the db cluster, since your CF cluster is already taken care of. For the moment, you should probably be running a second instance of SQL on one of the CF servers, or another spare server. You should be doing something like logshipping, so that in the event of failure of the SQL server, you can quickly get things up and running again, with minimal data loss. I'm not sure if the SQL license allows running a backup server with the same license, but you can always run SQL Express, assuming your database doesn't exceed the 4gb limitation. Russ > -----Original Message----- > From: Peterson, Chris [mailto:[EMAIL PROTECTED] > Sent: Monday, January 29, 2007 9:47 AM > To: CF-Talk > Subject: RE: Cluster File Management > > Well, I am running SQL 2005 Std (which supports clustering), but I would > need another SQL 2005 Std license to do a true fault tolerant cluster. > > I don't think, without a ton of cash, you will get a true complete fault > tolerant setup. You would need 2 different web service providers, 2 > separate hosting locations, a web cluster, a DB cluster, etc. Currently > my client runs on a very over-shared SQL server and 1 web server, shared > bandwidth, and they are generating about 10 gigs of IIS logs every 2 > weeks. We are moving them to dual web servers sharing one file source > behind a Cisco content switch, and a dedicated SQL 2005 box, with a > dedicated T3 line (not all committed rate, but burstable up to the full > T3 rate). Its only a single web provider, but we do have a sonnet fiber > loop coming right into the server room, so it's at least a redundant > line coming up both sides of the road. The web servers will run local > jRun clusters, so if I need to make server changes I can do it > per-instance and restart that instance without end users seeing any down > time. True, its not completely fault tolerant, and is dependant on a > single SQL server (which I cannot control), but I think in my current > environment it's the best I can get =) > > Chris Peterson > > -----Original Message----- > From: Russ [mailto:[EMAIL PROTECTED] > Sent: Monday, January 29, 2007 9:42 AM > To: CF-Talk > Subject: RE: Cluster File Management > > Great idea setting up a clustered environment, and then making it all > dependent on a single server. > > Not only will this be slow, if the SQL server goes, so does the rest of > the > site. But then again, this is probably already the case since you're > probably running the standard version of SQL server which doesn't > support > clustering. > > We are in the same boat with the SQL server, and I'm hoping to > eventually > move off it and go to something like MySQL which supports clustering for > free. > > Either way, if you plan on making your clustered environment last, you > probably should not be serving files out of a file share. DFS is a good > solution, when it works. > > Russ > > > -----Original Message----- > > From: Peterson, Chris [mailto:[EMAIL PROTECTED] > > Sent: Monday, January 29, 2007 9:24 AM > > To: CF-Talk > > Subject: RE: Cluster File Management > > > > I am going to setup a 3rd server (the SQL box) as the source of all > the > > files, and point IIS's home folder to 'a share on a remote machine', > and > > use a file share on the SQL box. Be sure to setup user security so > the > > web boxes can access those files on your file server, and then I will > > turn on trusted cache, so it only needs to grab the file from the > remote > > box once. Of course, if you make any changes you will have to force > CF > > to get your new page, but in production you shouldn't need to make > that > > many changes. =) Then I can just add in additional servers pointing > to > > the same source share, and they will never get out of sync. > > > > Chris Peterson > > > > -----Original Message----- > > From: WebSite CFtalk [mailto:[EMAIL PROTECTED] > > Sent: Monday, January 29, 2007 9:14 AM > > To: CF-Talk > > Subject: RE: Cluster File Management > > > > Hi, > > > > With Win2003 STD on both servers you can do that using DFS. > > > > Helge Hetland > > WebSite AS > > > > > > -----Original Message----- > > From: James Buckingham [mailto:[EMAIL PROTECTED] > > Sent: 29. januar 2007 11:58 > > To: CF-Talk > > Subject: Cluster File Management > > > > Hi everyone, > > > > Does anybody know any good sites / ref. books which talk about file > > management on a clustered environment? I've got two new load balanced > > servers which I'm currently migrating/recoding for (in CFEclipse) but > I > > want to some how automate the update processes on both servers. > > > > I.e. I make a change to a file on one server and it updates the same > > file on the other server automatically. > > > > The servers are Win 2003. > > > > Cheers, > > James > > > > > > > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:267947 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
