Novell Brainshare 2010 Amsterdam

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

3. High-Availability and Fault Tolerance

9. MTTR: 1 hour

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

18. Document repair procedures and train personnel

19. Chose Open Enterprise Server– Linux Server with Novell Cluster Services ™

21. Depends on failure detection time, restart time, overhead

22. Novell Cluster Services ™

24. Load distribution over multiple servers when having multiple resources

25. Monitors LAN and SAN/Storage connectivity – in the event of a failure – fences the problematic node and relocates the resource

26. Supports active-passive clustering

27. Supports resource monitoring

28. Supports Linux and Novell ® Open Enterprise Server services

29. Supports up to 32 nodes per cluster

32. Unload Script

34. Command Line Interface

35. E-mail and SNMP Notification

36. Integration with Novell ® Open Enterprise Server Services

37. Integration with XEN

38. Novell Cluster Services ™ Ctrl 2 Dual NICs Dual HBAs LUN 0 LUN 1 LUN … Ctrl 1 LAN Fabric SAN Fabric Storage Array Storage Array Novell iSCSI Storage Array Typical NCS 1.8 Architecture Fibre Channel or iSCSIl Ethernet

41. XEN virtualization support

44. Much faster

45. Much lower system load

47. AFP

48. …

52. Ability to edit resource priority list as text

53. Various UI improvements

54. Ability to disable resource monitoring (for Maintenance)

57. GroupWise ®

59. XEN guests (DomU) resources

60. Each resource is a server in its own right

61. Live migration with para-virtualised DomU

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

63. Best Practices Deploying Cluster Services

65. DHCP, DNS

66. Novell ® GroupWise ®

67. Novell ZENworks ®

68. XEN VMs

72. Configuration

75. All Servers in a cluster must be identical

76. Filesystem layout

77. Install only required patterns

78. Use local time

79. Default runlevel=3

81. Patch

82. Configure

86. /etc/multipath.conf and /etc/multipath/bindings

89. Standardize IP addresses

90. Virtual IP (Service-Lifetime address) instead of secondary IP?

92. Fault tolerant time synchronization

96. Use additional LUNs to expand existing pools

97. Maximum size (restore speed and allowable recovery time)

98. Define rules (ex. max. 80% fill-rate)

100. Load Balancing

101. Fan-out Failover

103. Novell Storage Services ™

105. Verify performance and utilization

109. Everything with I/O

110. What is Clusterable?

112. Use NSSMU

114. Delete resource for shadow

115. Modify load script for primary

117. Can be used for iPrint, DHCP etc

118. Use evmsgui to create and format the volume

119. Create the resource in iManager

123. Novell Storage Services ™ /POSIX rights

124. exportfs in load script rather then /etc/exports on nodes

125. Use fsid=x for Novell Storage Services

126. NFS Access SHARED1 Virtual Server shared1.beds.ac.uk 194.80.216.101 SHARED1 Volume NFSaccess Iface UID: 1012 Mis-dweeb UID: 1004 LUM NSS Rights Dweeb Gromit Wallace NFS FPC1 FPC2 FPC3 FPC4 FPC5 fpc.server.luton Mis UID: 1010 Oracle UID: 60003 Mis UID: 1010 Oracle UID: 60003 Iface UID: 1012 Mis UID: 1010 Oracle UID: 60003 Iface UID: 1012 Mis UID: 1010 Oracle UID: 60003 Iface UID: 1012

128. Run iprint_nss_relocate on each node with volume in place

129. NB: only one iPrint resource may run on a node

130. Need to accept certificates in iManager for each node

133. Check NCP:NCPServer objects

134. LUM user required for Novell Storage Services rights

136. Leases file on Novell Storage Services volume

138. Logrotate configuration

139. Default AppArmor configuration will not allow logging to here!

141. Ensure no Salvage when creating Volume

143. Run /noatime=volname

145. /etc/ocfs2/cluster.conf automagically created by Novell Cluster Services ™

146. Fstab mounting uses /etc/init.d/ocfs2 service

147. Required for XEN guests

148. SLOW!!!

149. DEMO

153. Modify load script for primary

156. Edit /etc/opt/novell/grpwise/gwha.conf - show=yes

157. Start GroupWise Agents one at a time

158. Comment out gwha.conf change

159. Question and Answer

160. www.nds8.co.uk

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.

164. There is no service

166. Rather no service than risk loss of corruption of data!

168. Application service

169. Typically, only one service instance at a time is allowed to run

171. non-cluster-aware file system mount

172. database instance

173. SAP R/3

174. ...

176. Nodes will lose power, hardware will die, memory corruption will occur, not even time keeping is guaranteed

177. The network loses, corrupts, delays and reorders data

178. Some nodes will receive a packet, others will not

180. You cannot trust anything or anyone

181. No 100% perfect solution is possible