january 8, 2009 business continuity cluster always running gregg a. hinchman consultant hinchman...

18
January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting [email protected] m

Upload: agnes-morgan

Post on 05-Jan-2016

218 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

January 8, 2009

Business Continuity Cluster Always Running

Gregg A. HinchmanConsultantHinchman [email protected]

Page 2: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell Inc.

2

Presentation Outline

I.Introduction

A.Panel Experts

B.Presentation Business

II. Knowledge Transfer

A.Definitions

B.Tools

III. BCC Forum

A.Business Analysis and needs -RTO/RPO

B.SAN's and Sites

C.Planning and Designing

D.Software and Scripting

E.LUN's

F. GroupWise

IV.Summary

Page 3: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell Inc.

3

Introduction: Panel Experts

• 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 Coolsolutions Articles -Consultants Corner

> GroupWise Advisor Magazine Articles

Page 4: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell Inc.

4

Introduction: Panel Experts

• 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

Page 5: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell Inc.

5

Introduction: Panel Experts

• Jim Petersen

– Novell WSS Consulting Resolution Engineer

– 14+ years NetWare OS Experience

– 5+ years Novell Clustering experience

– OS Bootcamp Instructor

– CNE6, MCNE, LPI2

Page 6: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell Inc.

6

Introduction: Presentation Business

• Topic

– We will discuss Business Continuity Clusters.

• Format

– Discussion will be led with LOTS of attendee participation -we hope.

• Questions

– Please ask!

• Knowledge:

– Clustering

• Related Sessions:> TUT315 -How to build a Highly Available GroupWise 7 system

Page 7: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell Inc.

7

Knowledge Transfer

• Definitions– Disaster

– BCC

– RTO -Recovery Time Objective

– RPO -Recovery Point Objective

– Synchronous

– Asynchronous

– High Speed Link

– Active and Passive

• Tools– iManager

– IDM

– DNS/DHCP/SLP -. . . is only as good as . . .

Page 8: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell Inc.

8

Knowledge Transfer

Novell Services

Business Continunity Cluster

File Share

s

GroupWis

e

Printing

Novell Services

File Share

s

GroupWis

e

Printing

Novell Services

File Share

s

GroupWis

e

Printing

Step1

Primary SiteFailure

Step2

Novell ServicesRun on Second

Site

Step3

-Potential-Second Site

Failure

Step4

Novell ServicesRun on Third

Site

Novell ServicesFail Over to Third Site

Novell ServicesFail Over to Second Site

Data CenterOne

Data CenterTwo

Data CenterThree

HighSpeedNetwork

X X

Page 9: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell Inc.

9

BCC Forum

• Business Analysis and needs -RTO/RPO• SAN's and Sites

– How Many Sites? Where are the sites?

– What SAN's?

• Planning and Designing– What/Where/When/Why/How

– eDirectory Design

– Active/Passive vs. Active/Active

– Mirroring -Asynchronous vs. Synchronous

– VLAN's or Not

Page 10: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell Inc.

10

BCC Forum

Cluster Sites 2

SAN

Identity Mgr.

Cluster Site 1

eDirectory

Disk Blocks

Building A Building B

Ethernet Switch Ethernet Switch

Fiber Channel Switch Fiber Channel Switch

Page 11: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell Inc.

11

BCC Forum

{root}

DEMO

SERVICES

BCC-Site1

BCC-Site2

BCC- Cluster

Cluster Nodes

Cluster Resources

IDM DriversLanding Zone

Landing Zone

BCC- Cluster

Cluster Nodes

Cluster Resources

IDM Drivers

Page 12: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell Inc.

12

BCC Forum

• Software and Scripting

– Clustering

– SMI-S

– Non-SMI-S work arounds

• LUN's

– 1 LUN to 1 Cluster Resource (Pool) to 1 Volume

• GroupWise

• Cost

Page 13: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

Questions?

Page 14: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell Inc.

14

Summary

• Planning

• Documenting

• Knowledge and Expertise

• Consultants -SAN and BCC

Page 15: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com
Page 16: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

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

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

Page 17: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell Inc.

17

Color Palette

RGB224 0 0

RED

RGB230 120 20

ORANGE

RGB98 158 31

GREEN

RGB28 130 185

BLUE

RGB60 60 65

RGB90 90 100

RGB204 204 205

GRAY

Note:The gray dotted-line box represents the margins or “working area” into which all text and most graphics and diagrams should conform.

How to Add Novell Colors to Your OpenOffice Color Palette:1. Go to the “Tools” menu2. Select “Options”3. Expand “OpenOffice.org”4. Select “Colors”5. Delete existing colors (one-by-one)6. Add Novell Colors by giving them a name and entering RGB values7. Click “OK”

Page 18: January 8, 2009 Business Continuity Cluster Always Running Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell Inc.

18

Graphics & Typeface

RED

ORANGE

GREEN

BLUE

GRAY

Icons/Lines: This presentation refresh simplifies the current template and pushes focus on the content being presented. The icon library will continue to be utilized, but a refresh will be noticeable with the removal of the dotted lines around each icon, and a subtle color shift. These icons are created to provide a professional, consistent look. When these icons are used sparingly, and in direct relation to the content on the slides, our presentations will communicate and work more effectively.

Note:

Typeface: Arial has been selected as the new typeface for all Novell communications. The following were considered. 1. Our typeface needs to be designed to carry information quickly to the reader.2. It needs to be usable for Novell employees in company correspondence and presentations, as well as for outside vendors for marketing and promotion.3. It needs to easily function on the Linux, Windows and Macintosh platforms. 4. And finally, Arial was created for these exact purposes.

Download Icon Library at: http://innerweb.novell.com/brandguide

How to Add Novell Icons to OpenOffice Gallery:1. Go to the “Tools” menu2. Select “Gallery”3. In the Gallery window select “New Theme...”4. With the “General” tab active name your new theme (ie.Red flat)5. Select the “Files” tab.6. Select “Find Files...”7. Find the downloaded folder containing the icons named and click “Select”8. Select “Add All” and then “OK”9. Repeat for all icon groups