>From what I've seen, a lot of that information is usually kept in the user's browser via cookies or "session cookies." For things that aren't, mirroring the data on separate physical devices, on separate controllers, etc., etc., provides the redundancy needed. The whole point of clustering is not to have _any_ single points of failure. That's why clustering an application is _at least_ two times more expensive than not clustering it.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfied Sent: Thursday, July 27, 2006 8:37 PM To: [email protected] Subject: Re: Bad Linux backups David Boyes wrote: > I think Lea means: > > For cluster takeover to work seamlessly, your application has to keep > session data in some common location between the servers. There's the point that has me: how do you backup that location? Is it something that, if it fails, you quickly find a new one and tell the PC buyer you had a "technical problem" and would they mind starting again? -- Cheers John ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
