34
January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise® 7 System Gregg A. Hinchman Consultant Hinchman Consulting [email protected] om

January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting [email protected]

Embed Size (px)

Citation preview

Page 1: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

January 8, 2009

How to Build a Highly- Available, Fault Tolerant GroupWise® 7 System

Gregg A. HinchmanConsultantHinchman [email protected]

Page 2: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

2

Presentation Outline

• Introduction– Speaker– Presentation Business

• Knowledge Transfer– Theory– Terms and Tools

• Recommendations– GroupWise® Re-design

> Domains

> Post Offices

> Gateways

– Clustering– Business Continuity

• Summary

Page 3: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

3

Introduction: Speaker

• 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 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

4

Introduction: Presentation Business

• Topic – We will discuss how to design a GroupWise® 7 system to be highly available

and fault tolerant.

• Format– Discussion will be led with supporting examples given.

• Questions– Please hold until 'Question Breaks'

• Knowledge:– Advanced GroupWise 7– Clustering Theory

• Related Sessions:> TUT216 -Consultants Corner: GroupWise Best Practices

> BOF100 -Birds of a Feather: Business Continuity Clusters

> SP275 A Hands-on Approach to Implementing an Effective Email Retention Solution with GroupWise and GWArchive

> SP276 Successful Deployment Strategies to Tackle Email Compliance Requirements and "Storage Bloat"

Page 5: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

5

Knowledge Transfer

• Theory– Business Continuance

– More the Merrier

– Cost of Downtime

• Terms and Tools– Highly Available vs. High Availability

– Fault Tolerant vs. Fault Resilient

– Webster: relaxed, patient, understanding vs. elastic/flexible, tough, resistant

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

Page 6: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

Questions?

Page 7: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

7

Recommendations: GroupWise® Redesign

• Domains– Primary

– More than 1 please

– Too many

– Mesh Topology Design

– Special Purpose Domains

Page 8: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

8

Recommendations: GroupWise® Redesign

Demo CompanyExample of a Best Practice Domain Designs

Key:

ConnectionTCP/IP

GWIA WebAccess DomainPostOffice

WADOM1

WADOM2

WADOM3

WADOM5

WADOM6

WADOM7

WADOM4

WADOM8

IADOM1

IADOM2

IADOM3

PODOM1

PODOM2

PODOM3

PMDOM(Primary Domain)

Page 9: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

9

Recommendations: GroupWise® Redesign

• Post Offices– Just 1

– More than 1

– Too many

– Special Purpose Post Offices> Document Management

> Resources/Distribution Lists

Page 10: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

10

Recommendations: GroupWise® Redesign

Demo CompanyExample of a Best Practice Post Office Designs

Key:

Connection

TCP/IP

GWIA WebAccess DomainPostOffice

PODOM1

PODOM2

PODOM3

PO 1(1000 users)

PO 3(1000 users)

PO 7(1000 users)

PO 2(1000 users)

PO 4(1000 users)

PO 8(1000 users)

PO 5(1000 users)

PO 9(1000 users)

PO 6(1000 users)

PO 10(1000 users)

Page 11: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

Questions?

Page 12: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

12

Recommendations: GroupWise® Redesign

• Gateways -GWIA– Its own domain

– 2 GWIA's > Highly Available

> Fault Tolerant

– 2 GWIA's> High Availability

> Fault Resilient

– Special Purpose GWIA's> POP3/IMAP

> Internal ONLY

– The Border> 2 Points of Entry

> AntiSpam/AntiVirus Appliance -GWGuardian

> DNS

Page 13: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

13

Recommendations: GroupWise® Redesign

Demo CompanyHighly Available GWIA

Key:

GWIA WebAccess DomainPostOffice

IADOM1

IADOM2

IADOM3

GWIA 1 GWIA 2 GWIA 3

TCP Port(Fault Tolerant)

TCP Port(Fault Tolerant)

GWGuardian

AntiVirus/AntiSpam

Filters

GWGuardian

AntiVirus/AntiSpam

Filters

Firewall

Internet

Page 14: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

14

Recommendations: GroupWise® Redesign

Page 15: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

Questions?

Page 16: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

16

Recommendations: GroupWise® Redesign

• Gateways -WebAccess Agent– Its Own domain

– 250 to 500 users per Agent

– Disposable Gateway

– 2+ WebAccess Agents> Highly Available

> Fault Tolerant

– 2+ WebAccess Agents> High Availability

> Fault Resilient

Page 17: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

17

Recommendations: GroupWise® Redesign

• Gateways -WebAccess Application– Up to 1000 users

– 2 or more> Highly Available

> Fault Tolerant

– 2 or more> High Availability

> Fault Resilient

– Content Switches/DNS

Page 18: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

18

Recommendations: GroupWise® Redesign

Page 19: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

19

Recommendations: GroupWise® Redesign

Demo CompanyHighly-Available WebAccess Design

Key:

GWIA WebAccess DomainPostOffice

WA1

Firewall

Internet

PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10

Email Processing

WA2 WA3 WA4 WA5 WA6 WA7 WA8

WebAccessApplication

1

WebAccessApplication

2

WebAccessApplication

3

WebAccessApplication

4

Login Handoff

WebServer1

Layer 4(Content Switch)Load

Balance/Fault Tolerance

WebServer4

Layer 4(Content Switch)Load

Balance/Fault Tolerance

Firewall

Internet

WebServer2

WebServer3

Fault Tolerant/Load Balancing Handoff

Webm

ail.domain.com

Web

mail

.dom

ain.co

m

Page 20: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

Questions?

Page 21: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

21

Recommendations: Clustering

• What's a Cluster?• Why Cluster?• Where Cluster?

– Consolidations into centralized data centers

– Disaster Recovery Sites

• OES NetWare® vs. OES Linux Clusters• Planning and Documenting• Proper Implementation• Fibre Channel vs. iSCSI

Page 22: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

22

Recommendations: Clustering

Demo CompanyGroupWise Cluster Design

PMDOMVSCluster Resource

PODOMVSCluster Resource

EMAILPOVSCluster Resource

DMSPOVSCluster Resource

192.168.20.101 192.168.20.102 192.168.20.103 192.168.20.104

PMDOMVSCluster Resource

PODOMVSCluster Resource

EMAILPOVSCluster Resource

DMSPOVSCluster Resource

192.168.20.105 192.168.20.106 192.168.20.107 192.168.20.108

PMDOM

MTA

PODOM

MTA

EMAILPO

POA

EMAILPOM

POA

GroupWise

Library

WADOM

MTA

WA IADOM

MTA

GWIA Messaging Agent

Messaging

ArchiveAgent

Apache2/

Tomcat4

WebAccessApplication

Page 23: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

23

Recommendations: Clustering

Page 24: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

24

Recommendations: Clustering

Page 25: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

25

Recommendations: Clustering

PMDOMVSCluster Resource

PODOMVSCluster Resource

IMVSCluster Resource

EMAILPOVSCluster Resource

192.168.20.101 192.168.20.102 192.168.20.109 192.168.20.103

DMSPOVSCluster Resource

IADOMVSCluster Resource

WADOMVSCluster Resource

WAVS1Cluster Resource

192.168.20.104 192.168.20.106 192.168.20.105 192.168.20.107

PMDOM

MTA

PODOM

MTA

EMAILPO

POA

GroupWise

Library

WADOM

MTA

WAIADOM

MTA

GWIA

Messaging Agent

Messaging Archiv

eAgent

Apache2/

Tomcat4

WebAcce

ssApplicatio

n

OESNW1

OESNW2

OESNW3

X

POA

EMAILPO

Page 26: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

Questions?

Page 27: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

27

Recommendations: Business Continuity

• What's a Business Continuity Cluster (BCC)?• Why Business Continuity Cluster?• Where to BCC?

– Multiple Sites

– Disaster Recovery Sites

• Considerations and Cost• Fibre Channel SANs• High Speed Links• SAN-based Data Synchronization

Page 28: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

28

Recommendations: Business Continuity

Novell Services

Business Continunity Cluster

File Shares

GroupWis

e

Printing

Novell Services

File Shares

GroupWis

e

Printing

Novell Services

File Shares

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 29: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

29

Summary

• Business Analysis• What can you afford?• What can you do for 'free'?• Plan, Plan, Plan• Document, Document, Document• Training• Hire the Expertise

Page 30: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

Questions?

Page 31: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com
Page 32: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System 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.

Page 33: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

33

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 34: January 8, 2009 How to Build a Highly- Available, Fault Tolerant GroupWise ® 7 System Gregg A. Hinchman Consultant Hinchman Consulting gregg@HinchmanConsulting.com

© Novell, Inc.

34

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