Josh,
I have not used MySQL cluster, but it is explained well in the online
docs. It requires at least a half-dozen computers or more to offer
the redundancy that motivates its use. The advantage of a cluster is
that a node in the cluster in the server can fail and at worst a
couple of transactions get rolled back, but otherwise the cluster
keep running with no downtime, major data loss and no subsequent data
recovery downtime.
Standard replication requires 2 computers at least, provides data
loss protection and is very very easy to set it up.
Here is updated replication setup instructions from my upgrade to 4.1
yesterday. Much easier now with version 4.1.
http://homepage.mac.com/kelleherk/iblog/C711669388/E20061027215152/
index.html
Anyway HTH,
-Kieran
________________________________________________________________
Blog: http://webobjects.webhop.org/
Dev Config = OS X 10.4.8 MBPro-Intel / Java 1.4.2_09 / WO 5.3.1 & P.
Wonder / XCode v2.2.1 / MySQL 4.1.21-std / Connector-J 3.0.17
Deploy Config = WO on OS X 10.3.9 Server G4-PPC / Java 1.4.2_09 / WO
5.2.3 / Connector-J 3.0.17 / MySQL 4.1.21 on OS X 10.4.8
On Nov 1, 2006, at 1:15 AM, Joshua Paul wrote:
What solutions have people here used to deal with database or
hardware failures? Has anyone tried or deployed using MySQL
Cluster? If so, what pitfalls/hurdles did you encounter?
--
josh
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%
40mac.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
