> > I see. So many variables that it's hard to offer an > opinion. I guess > > if you look at the history of the application and it's future > > requirements and assess how this technique would add value, > that would > > give you the information you need. Maybe try it with a > small app first > > and get some experience with it, before using it for larger apps. > > Bill this is CYA from the company POV. > > I am setting this up on my test servers to see how well they > fail over in a real world condition. I'll pull the data > cables off the primary machine in test one. Test two I'll > pull the power cords. > > Does the cluster respond to loss of the primary and fail over > to the secondary right away? How much down time could I > expect till it happens? Does it work without human > interaction properly?
I can give you one scenario where it's problematic: a very large real-time database application where a software error is introduced. In this case, not only will you have to repair the primary database (in real time or not), but you'll also have to quiese the application to regenerate the mirror. This can be a gotcha if the database is really large. Bill _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
