I have to put together a proposal for a medical office management
application which will be used in an ASP (application service provider -
not the MS language:) model.. one of the requirements is that the
application has to be hosted in such a way that a major disaster (natural
or otherwise) in 1 location can't cause the loss of any data, and only a
small (maybe an hour) downtime for the application.
After the Sept. 11 tragedy, my websites had connectivity problems on
and off for a few days. We also had 24 hours of downtime when a hurricane
knocked down a bunch of telephone poles near my ISP a few years ago.
For this application, that wouldn't have been acceptable.
I have no idea how to approach it. Any ideas?
Al
a1webs.com
At 06:08 PM 5/10/2002 -0400, Justin Greene wrote:
>I Have to agree. Hardware based clustering for the front end... and either
>SQL Enterprise or Veritas on the backend to handle the database cluster.
>Very solid configuration. We have been hardware clustering CF with Alteons
>for over 3 years. Just need to keep sessions in the DB and make sure the
>web boxes keep the file systems synched.
______________________________________________________________________
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
