the art of business continuance brad rupp wg storage engineering novell [email protected]...
TRANSCRIPT
The Art of Business Continuance
Brad RuppWG Storage EngineeringNovell
Gregg A. HinchmanConsultantHinchman [email protected]
© Novell Inc. All rights reserved
2
IntroductionPresentation Outline
• Introduction– Speakers– Presentation Business
• Planning– Definitions and Tools– Design
• What's New for Business Continuity Clustering 1.1?
– Prerequisites– New Features/Benefits
• Summary
© Novell Inc. All rights reserved
3
IntroductionSpeakers
• 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
© Novell Inc. All rights reserved
4
IntroductionSpeakers
• Gregg A. HinchmanSelf-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
© Novell Inc. All rights reserved
5
IntroductionPresentation 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®
© Novell Inc. All rights reserved
6
IntroductionPresentation 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
© Novell Inc. All rights reserved
7
PlanningDefinitions 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)
© Novell Inc. All rights reserved
8
Planning Definitions and ToolsWhat is Business Continuity Clustering?
Building A Building B
Server1a Server2a Server3a Server4a Server1b Server2b Serve3b Server4b
Fibre ChannelDisk Array
Fibre ChannelDisk Array
Fibre ChannelSwitch
Fibre ChannelSwitch
WAN
SAN
DiskBlocks
Ethernet Switch Ethernet Switch
Cluster Site 1 Cluster Site 2
Two Independent clusters atgeographically separate sites
eDirectory™
DirXML
© Novell Inc. All rights reserved
9
Planning Definitions and ToolsWhat is Business Continuity Clustering?
Step1
Primary SiteFailure
Novell Services
GroupWise
PrintingFileShares X X
Novell Services
GroupWise
PrintingFileShares
Novell Services
GroupWise
PrintingFileShares
Step2
Novell ServicesRun On 2nd
Site
Step3
~ Potential 2nd
Site Failure ~
Novell Services FallOver to 3rd Site
Step4
~ Potential 2nd
Site Failure ~
Novell Services FallOver to 2rd Site
Data CenterOne
High Speed Network
Data CenterTwo
Data CenterThree
Business Continuity Cluster
© Novell Inc. All rights reserved
10
PlanningDesign
• 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
Questions and Answers
© 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?
© 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
© 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)
© 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.
© 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?
© 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
Questions and Answers
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 DisclaimerThis 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