1. The Art of Business Continuance Brad Rupp WG Storage Engineering Novell brupp@novell.com brupp@novell.com Gregg A. Hinchman Consultant Hinchman Consulting gregg@hinchmanconsulting.com

2. © Novell Inc. All rights reserved 2 Introduction Presentation Outline Introduction – Speakers – Presentation Business Planning – Definitions and Tools – Design What's New for Business Continuity Clustering 1.1? – Prerequisites – New Features/Benefits Summary

3. © Novell Inc. All rights reserved 3 Introduction Speakers Brad Rupp Senior Software Engineer, Novell ®, Inc. Team lead, Novell Business Continuity Cluster development Architect, Novell Business Continuity Cluster Team member, Novell Cluster Services development Not so cool blogger http://www.novell.com/coolblogs/?author=37

4. © Novell Inc. All rights reserved 4 Introduction Speakers Gregg A. Hinchman Self-Unemployed Consultant, www.HinchmanConsulting.com 11+ years of GroupWise ® Experience 5 years of Clustering experience Author: > “Success with Clustering GroupWise 7” www.TayKratzer.com Co-Author: > “Success with GroupWise Document Management” GroupWise ® Cool Solutions Articles > Consultants Corner GroupWise Advisor Magazine Articles

5. © Novell Inc. All rights reserved 5 Introduction Presentation Business Topic – We will discuss Novell ® Business Continuity Cluster 1.1. Format – Discussion will be led with supporting examples given. Questions – Please hold until 'Question Breaks' Knowledge – Advanced Cluster Knowledge – Open Enterprise Server Linux/NetWare ®

6. © Novell Inc. All rights reserved 6 Introduction Presentation Business Related Sessions: – Consultants Corner: Successful GroupWise ® 7 Consolidations – TUT109: Clustering GroupWise 7 on Open Enterprise Server Linux – TUT202: Migrating a NetWare ® cluster to an OES Linux cluster – BUS320: Business Continuity Clustering Deployments Solutions lab "Stop by table A-10" (this is the Business Continuity Clustering" table

7. © Novell Inc. All rights reserved 7 Planning Definitions and Tools Definitions – Disaster – BCC – RTO -Recovery Time Objective – RPO -Recovery Point Objective – Synchronous and Asynchronous – High Speed Link – Active and Passive – LUN's > 1 LUN to 1 Cluster Resource (Pool) to 1 Volume Tools – iManager – IDM – DNS/DHCP/SLP -... is only as good as... – Dynamic routing (RIP/OSPF)

8. © Novell Inc. All rights reserved 8 Planning Definitions and Tools What is Business Continuity Clustering? Building ABuilding B Server1aServer2aServer3aServer4aServer1bServer2bServe3bServer4b Fibre Channel Disk Array Fibre Channel Disk Array Fibre Channel Switch Fibre Channel Switch WAN SAN Disk Blocks Ethernet Switch Cluster Site 1Cluster Site 2 Two Independent clusters at geographically separate sites eDirectory ™ DirXML

9. © Novell Inc. All rights reserved 9 Planning Definitions and Tools What is Business Continuity Clustering? Step 1 Primary Site Failure Novell Services GroupWise PrintingFile Shares XX Novell Services GroupWise PrintingFile Shares Novell Services GroupWise PrintingFile Shares Step 2 Novell Services Run On 2 nd Site Step 3 ~ Potential 2nd Site Failure ~ Novell Services Fall Over to 3 rd Site Step 4 ~ Potential 2nd Site Failure ~ Novell Services Fall Over to 2 rd Site Data Center One High Speed Network Data Center Two Data Center Three Business Continuity Cluster

10. © Novell Inc. All rights reserved 10 Planning Design Business Analysis and needs -RTO/RPO SANs and Sites – How Many Sites? – Where are the sites? – What SAN's? Implementation Planning – What/Where/When/Why/How – eDirectory ™ Design – Active/Passive vs. Active/Active – Mirroring -Asynchronous vs. Synchronous – Network Infrastructure and VLANs or Not

11. Questions and Answers

12. © Novell Inc. All rights reserved 12 What's New with Business Continuity Clustering 1.1, Prerequisites Data replication – SAN vs. Host based mirroring – Network Link between sites – Fiber distance between sites – Synchronous or Asynchronous – Storage Management Initiative Specification (SMI-S) or SAN specific proprietary management software eDirectory ™ – One tree or multiple trees? Identity Manager (IDM) – What about single trees?

13. © Novell Inc. All rights reserved 13 What's New with Business Continuity Clustering 1.1, Prerequisites OES Linux – Version and patches > See the requirements page of the documentation – OpenWBEM – Linux User Management > LUM enabled users and groups – User for inter-cluster communication > eDirectory ™ rights > Credentials

14. © Novell Inc. All rights reserved 14 What's New with Business Continuity Clustering 1.1, Features/Benefits Open Enterprise Server NetWare ® – Version and patches > See the requirements page of the documentation > LibC – OpenWBEM – User for inter-cluster communications > eDirectory ™ rights > File system rights – Mixed operating systems (Linux and NetWare)

15. © Novell Inc. All rights reserved 15 What's New with Business Continuity Clustering 1.1, Features/Benefits SMI-S Support – Perl based Common Information Model (CIM) client – Load and unload – Extensible (e.g. Dynamic DNS) – Support for vendor specific management technologies – Involve your SAN vendor. They are the experts.

16. © Novell Inc. All rights reserved 16 What's New with Business Continuity Clustering 1.1, Features/Benefits Auto Fail Over – Monitors > Node count > Node percentage > Connection timeout > Ping (future) > Other – How it works – What can go wrong – Auto fail over vs. manual fail over – which is better?

17. © Novell Inc. All rights reserved 17 Summary Define Business Needs and Requirements Plan the Implementation Document the Plan Acquire the Expertise – Training – Consultants (need expertise in both BCC and the SAN) – SAN Vendor Regularly test the plan

18. Questions and Answers

20. 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