Ajcody-Clustering: Difference between revisions
mNo edit summary |
|||
Line 4: | Line 4: | ||
===Actual Clustering Topics Homepage=== | ===Actual Clustering Topics Homepage=== | ||
---- | |||
Please see [[Ajcody-Clustering]] | Please see [[Ajcody-Clustering]] | ||
===My Other Clustering Pages=== | ===My Other Clustering Pages=== | ||
---- | |||
* [[Ajcody-Notes-Upgrade-Options#Upgrade_Steps_for_Multi-Servers_with_Clustered_Mailstores]] | * [[Ajcody-Notes-Upgrade-Options#Upgrade_Steps_for_Multi-Servers_with_Clustered_Mailstores]] | ||
Line 13: | Line 17: | ||
===Good Summary For RHEL Clustering=== | ===Good Summary For RHEL Clustering=== | ||
---- | |||
This is a good solid summary about RHEL clustering: | This is a good solid summary about RHEL clustering: | ||
Line 19: | Line 25: | ||
===Active-Active Clustering=== | ===Active-Active Clustering=== | ||
---- | |||
There is a bug(rfe) for active-active configuration. Please see: | There is a bug(rfe) for active-active configuration. Please see: | ||
Line 25: | Line 33: | ||
===Non-San Based Fail Over HA/Cluster Type Configuration=== | ===Non-San Based Fail Over HA/Cluster Type Configuration=== | ||
---- | |||
This RFE covers issues when your wanting a "copy" of the data to reside on an independent server - LAN/WAN. | This RFE covers issues when your wanting a "copy" of the data to reside on an independent server - LAN/WAN. | ||
Line 33: | Line 43: | ||
===RFE's/Bug Related To Supporting Clustering Options=== | ===RFE's/Bug Related To Supporting Clustering Options=== | ||
---- | |||
* "Add VCS cluster support for Suse ES 10" | * "Add VCS cluster support for Suse ES 10" | ||
Line 52: | Line 64: | ||
===HA-Linux (Heartbeat)=== | ===HA-Linux (Heartbeat)=== | ||
---- | |||
References: | References: |
Revision as of 20:33, 16 November 2008
Clustering Topics
Actual Clustering Topics Homepage
Please see Ajcody-Clustering
My Other Clustering Pages
- Ajcody-Notes-Upgrade-Options#Upgrade_Steps_for_Multi-Servers_with_Clustered_Mailstores
- Ajcody-Notes-Of-Customer-Cluster-Upgrade
Good Summary For RHEL Clustering
This is a good solid summary about RHEL clustering:
http://www.linuxjournal.com/article/9759
Active-Active Clustering
There is a bug(rfe) for active-active configuration. Please see:
http://bugzilla.zimbra.com/show_bug.cgi?id=19700
Non-San Based Fail Over HA/Cluster Type Configuration
This RFE covers issues when your wanting a "copy" of the data to reside on an independent server - LAN/WAN.
Please see:
- "Disaster recovery through server to server sync (beta)"
RFE's/Bug Related To Supporting Clustering Options
- "Add VCS cluster support for Suse ES 10"
- http://bugzilla.zimbra.com/show_bug.cgi?id=24303
- SuSE Clustering resources - These might be useful.
- "Cluster Configuration on SLES"
- "Clustering Your Novell Groupwise Servers - Xen & Heartbeat2 on SLES"
- "SuSE paper about HA and Virtual Servers - PDF"
- What SLES has for clustering - Linux Virtual Server
- "Add support for otther cluster software lifekeeper and mc/service guard"
- "Add clustering support for Mac OS X"
HA-Linux (Heartbeat)
References:
HA-Linux How-To For Testing And Educational Use
References:
- HA-Linux Project Homepage
- Howto: Highly available Zimbra cluster using Heartbeat and DRBD
- DRBD Homepage
- DRBD currently unsupported at this time.
- 1. "disaster recovery through server to server sync (beta)"
- 2. "add active-active support to zcs" , marked as a dup of the above.
- DRBD currently unsupported at this time.
Actual HA-Linux How-To For Testing And Educational Use Homepage
Please see Ajcody-Notes-HA-Linux-How-To
Motive Behind How-To
I hope this gives an easy way to setup through some clustering concepts for an administrator to gain some real-world experience when they currently have none. I plan on walking through each "function" that is behind clustering rather than jumping to an end setup (Linux-HA, Shared Storage, And Zimbra).
The structure will be:
- Setup two machines (physical or virtual)
- Emphasis physical hostname / ip vs. the hostname and ip address that will be for HA.
- Setup virtual hostname and ip address for HA.
- Explain and do ip failover between the two machines.
- Setup a disk mount, we'll use probably use a nfs export from a third machine.
- This will give us an example of expanding the HA conf files to move beyond the ip address failover.
- Adjust HA conf's to now export via nfs a local directory from each server. This will not be a shared physical disk of course.
- Setup a shared disk between the two servers and include it in the HA conf files.
- Can use drbd or maybe figure out a way to share a virtual disk between the two vm's.
- Setup a very simple application to include between the two machines. Something like apache or cups.
- Go back and now readjust all variables between monitoring type (automatic) failover and simple manually initiated.