1. High-Availability with Novell Cluster Services ™ for Novell ® Open Enterprise Server on Linux Tim Heywood , CTO, NDS8 [email_address] Martin Weiss , Senior Technical Specialist [email_address] Dr. Frieder Schmidt , Senior Technical Specialist [email_address]
2. Agenda High Availability and Fault Tolerance Novell Cluster Services ™ Best Practices Deploying Cluster Services What is Clusterable? Demo
13. Availability of a parallel design: A par = 1 – ( 1 - A 1 ) * ( 1 – A 2 ); A par = 1 – ( 1 - 0.99 ) * ( 1 – 0.99 ); A par = 1 – ( 0.01 ) * ( 0.01 ) = 0.9999
14. “3R Rule” for High-Availability Systems R edundancy, R edundancy, R edundancy Fault Tolerance “The ability of a system to respond gracefully to an unexpected hardware or software failure.” Webopedia Computer System Fault Tolerance “The ability of a computer system to continue to operate correctly even though one or more of its components are malfunctioning.” Institute for Telecommunication Services, National Telecommunications and Information Administration, US Dept. of Commerce
62. XEN Cluster Architecture OCFS2 LUN DomU Files Cluster Node Xen Dom0 Cluster Node Xen Dom0 Cluster Node Xen Dom0 Resource DomU Linux iPrint Resource DomU Linux iPrint Resource DomU Linux iFolder Resource DomU Linux GroupWise Resource DomU NetWare pCounter Live Migrate Live Migrate
162. Unpublished Work of Novell, Inc. All Rights Reserved. This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability. General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.
Mean Time Between Failurs (MTBF) Mean Time To Failure (MTTF); Time to FIRST Failure (new components) = statistical metric that is only valid for a large number (batch) of a given component - follows a normal distribution - does not give any indication after what time a certain individual component (i. e. hard disk) will fail
Availability (365,2425 day year 365 + 0,25 - 0,01 + 0,0025 ) 98.01% 174,44 h of allowable down time 99% 87,66 h of allowable down time 99.5% 43,83 h of allowable down time 99.9% 8,77 h of allowable down time 99.99% 52,59 min of allowable down time 99.999% 5,26 min of allowable down time Think of a multi-segmented NSS pool as an example of a serial design. Think of a NIC team as an example of parallel design All systems are made up of a combination of serial and parallel components
Talk about creating the two pools and why. DEMO: Create pool1/vol1 Create pool1_shd/vol1_shd
Talk about creating the two pools and why. DEMO: Create pool1/vol1 Create pool1_shd/vol1_shd
Talk about creating the two pools and why. DEMO: Create pool1/vol1 Create pool1_shd/vol1_shd
Talk about creating the two pools and why. DEMO: Create pool1/vol1 Create pool1_shd/vol1_shd
Talk about creating the two pools and why. DEMO: Create pool1/vol1 Create pool1_shd/vol1_shd
Talk about creating the two pools and why. DEMO: Create pool1/vol1 Create pool1_shd/vol1_shd
Talk about creating the two pools and why. DEMO: Create pool1/vol1 Create pool1_shd/vol1_shd
Talk about creating the two pools and why. DEMO: Create pool1/vol1 Create pool1_shd/vol1_shd
Talk about creating the two pools and why. DEMO: Create pool1/vol1 Create pool1_shd/vol1_shd
Talk about creating the two pools and why. DEMO: Create pool1/vol1 Create pool1_shd/vol1_shd
Talk about creating the two pools and why. DEMO: Create pool1/vol1 Create pool1_shd/vol1_shd
Talk about creating the two pools and why. DEMO: Create pool1/vol1 Create pool1_shd/vol1_shd