510 likes | 731 Views
Introduction: Presentation Outline. IntroductionSpeakersPresentation BusinessPlanningDefinitions and ToolsBusiness AnalysisCluster and GroupWise
E N D
1. Success Centralizing and Clustering GroupWise®Bringing GroupWise to a Data Center Gregg A. Hinchman
Consultant
Hinchman Consulting
Gregg@HinchmanConsulting.com
2. Introduction: Presentation Outline Introduction
Speakers
Presentation Business
Planning
Definitions and Tools
Business Analysis
Cluster and GroupWise® Design
GroupWise Audit
Implementation
Move the GroupWise System
Redesign GroupWise System
Move User Mailboxes
Summary
3. Introduction: Speakers Gregg A. Hinchman
Owner/Consultant, www.HinchmanConsulting.com
12+ years of GroupWise® Experience
6 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 Series
GroupWise Advisor Magazine Articles
8 years BrainShare Presenter
5 years GroupWise Advisor Summit Presenter
4. Introduction: Presentation Business Topic
We will discuss Best Practices for Redesigning, Consolidating and Clustering GroupWise® 7
Format
Discussion will be led with supporting examples given
Questions
Please hold until 'Question Breaks'
Knowledge:
Advanced GroupWise
Clustering
Linux/NetWare®
5. Planning: Definitions and Tools Definitions
Consolidation –to reduce/collapse/merge together
Move –to pick up and place in a different location
Upgrade –to increase to a new version
Migrate –to change while moving
Cluster –a bunch of servers gathered round a Storage Area Network (SAN)
5 “9's” of Availability (99.999%)
Tools
Novell® Server Consolidation and Migration Utility
GroupWise® Server Migration Utility
GWCheck
Support.Novell.Com
Forums and Cool Solutions
USB Drive/Planes/Trains/Automobiles
Remote Desktop/VPN/GOTOMYPC.com
6. Planning: Business Analysis Reasons to Consolidate?
Old Style Design –Domain, PO, Gateway per remote site
Faster WAN Links
Virtualization of Servers
Decrease Administrative Staff
Decrease in GroupWise® Administration knowledge
Centralization of Services to Data centers
Clustering
Business Continuance
Disaster Recovery
Save $$$
7. Questions?
8. Next Up: Planning
9. Planning: Cluster and GroupWise® Design NetWare® Cluster Considerations
LUN's
SAN's –Support NetWare?
Proper Carving and LUN Placement
Naming Standards
Cluster Nodes
Virtual?
Naming Standards
Disk Space
Pools/Volumes
Naming Standards
10. Planning: Cluster and GroupWise® Design More NetWare® Cluster Considerations
Cluster Resources
Naming Standards –Consider with GroupWise in mind
IP Address Standards
Protected Memory
SET Commands for STARTUP.NCF
All Agents in own memory space
Naming Standards
SLP/HOSTS
11. Planning: Cluster and GroupWise® Design Linux Cluster Considerations
Knowledge
SLES or OES?
File Systems: Reiser, NSS, EXT3
iManager, NSSMU, EVMS
LUN's
SAN's –Support OES Linux?
Proper Carving and LUN Placement
Naming Standards
Cluster Nodes
Support OES Linux?
HBA's support OES Linux?
Naming Standards
12. Planning: Cluster and GroupWise® Design More Linux Cluster Considerations
Disk Space
Disk Segment
Volumes
Mount Points
Cluster Resources
Naming Standards –Consider with GroupWise in mind
IP Address Standards
SLP
13. Planning: Cluster & GroupWise® Design Linux Cluster Installation Tips for GroupWise
Agents must be installed on each cluster node
Why?? –RPM database issues
Log and Startup files are on cluster resource
Designate one node as the “install node”
On–line resource to “install node” prior to agent configuration
Or create a Cluster Resource for Software Distribution Directory – on–line to node for agent configuration
Import cluster data to all other nodes
Create mount points on appropriate cluster nodes
Can create mount point with cluster resource load script
“ignore_error mkdir /mnt/mountpoint”
14. Questions?
15. Planning: Cluster and GroupWise® Design TSATEST
Testing throughput to your SAN and LUN's
Set a Baseline Test to a local volume
Set a SAN test to a LUN on the SAN
Set a Network test to a local volume on a different server
Create Scripts to run the Commands
TID: 10092890
Documentation: OES Linux
http://developer.novell.com/documentation//samplecode/smscomp_linux_sample/tsatest/tsatest_linux.html#bswvivp
Article: OES NetWare
http://www.novell.com/communities/node/3085/consultants-corner-tsk-tsk-disk-disk
16. Planning: Cluster and GroupWise® Design NetWare® Scripts
BASETSATEST.NCF
load tsatest /V=VOL1: /PATH=\TSATTEST /U=.admin.demo /P=novell /I=5 /ERR=sys:\etc\tsaErr.txt
SANTSATEST.NCF
load tsatest /V=SANVOL1: /PATH=\TSATTEST /U=.admin.demo /P=novell /I=5 /ERR=sys:\etc\tsaErr.txt
CROSSTSATEST.NCF
load tsatest /S=FS2 /V=FS2VOL1: /PATH=\TSATTEST /U=.admin.demo /P=novell /I=5 /ERR=sys:\etc\tsaErr.txt
17. Planning: Cluster and GroupWise® Design Linux Scripts
BASETSATEST
./tsatest --path={PATH to local disk} -U {USERNAME) -P {PASSWORD} -I 5 --log{=LOGFILE}
SANTSATEST
./tsatest --path={PATH to attached SAN disk} -U {USERNAME) -P {PASSWORD} -I 5 --log{=LOGFILE}
CROSSTSATEST
./tsatest -s {SERVER} --path={PATH to local disk} -U {USERNAME) -P {PASSWORD} -I 5 --log{=LOGFILE}
18. Planning: Cluster and GroupWise® Design Virtualization of GroupWise
Yes, you can. Yes it works. Even on a cluster.
VMware ESX
Virtualize NetWare® and/or Linux
Virtualize a Cluster of NetWare and/or Linux
Xen Virtualization
SLES 10 sp1
SLES Virtual Machine Driver Pack -Windows OS's, RedHat 4,5
32 bit/64 bit
Virtualize NetWare 6.5 sp7 (as part of OES2)
Not all 'virtualized' servers on 1 VM box
Test Throughput
Test Network Throughput
19. Questions?
20. Planning: Cluster and GroupWise® Design Consider the Network Infrastructure
How are end users going to connect?
WebAccess/Caching/Online
Number of Users?
Number of Post Offices?
Number of Gateways?
Document the Design
Clustering –Use a GroupWise Cluster Design Matrix
21. Planning: Cluster and GroupWise® Design Example of Design Matrix for Cluster and GroupWise
22. Planning: Cluster and GroupWise® Design Post Office Sizing
23. Planning: Cluster and GroupWise® Design
24. Questions?
25. Planning: GroupWise® Audit (Health) Current Design
Hub, Mesh, Mixed Topology
Sizing –Users and 'On–Disk data'
Post Offices per Domain
Special Purpose Post Offices –DMS, Resources, etc.
Gateway Usage –POP, IMAP, EMAIL, etc.
Gateways per Domain
Pending Operations
User Move Status per domain, post office
Link Configuration
TCP/IP
NOT UNC
NOT MAPPED
26. Planning: GroupWise® Audit (Health) MTA
2nd Priority Threads
Bind Exclusively –IP Link Configuration and DNS
Ports –Standard vs. non–Standard
Verbose Logging Please
eDirectory™ User Sync
/Home–Volume:\directory
/TCPINBOUND-600+
/TCPTRUNKWIDTH-4 –NOT anymore!
Hard configure Ports/IP Addresses???
27. Planning: GroupWise® Audit (Health) POA
Bind Exclusively –IP Link Configuration and DNS
Ports –Standard vs. non–Standard
Verbose Logging Please
/Home–Volume:\directory
Scheduled Events –Contents with “attclip” –Orphaned Attachments –Bye Bye
Scheduled Events –Structure/Index and Fix
Hard configure Ports/IP Addresses???
28. Questions?
29. Next Up: Implementation
30. Implementation: Move the GroupWise® System NetWare® Cluster and the Novell® Server Consolidation Utility
Make sure SLP is properly configured
All Servers should have an SMDR entry in SLP
Make sure HOSTS file is filled in properly
Stage your move process
First, move it all at night/weekends (5-20+ hours)
Second, do delta's to keep the files up-to-date (2.5 to 10+ hours)
Third, move/cut over (2.5 to 10+ hours)
31. Implementation: Move GroupWise® Moving GroupWise from Server to Server
Connect to Domain being moved OR Post Office Domain
Change the UNC's –Post Office, Domain, Library Storage (if needed)
Change the SDD
Change the POA/MTA IP Address, ports (if needed)
Change the POA/MTA Log file path
Unload the Agents
Verify 'clean unlocked' status on DB's (wpdomain and wphost)
32. Implementation: Move the GroupWise® System Linux Cluster and the GroupWise Server Migration Utility
Move GroupWise Domains, Post Offices, Gateways
Move from NetWare® and/or Windows to Linux
Not Cluster Aware but Linux server can be member of cluster
Cannot Update to new version of GroupWise while migrating (unlike with the NW Server Consolidation Utility)
GroupWise 6.5 and 7
Source Servers:
NetWare 4.2 to 6.5 (OES)
Windows Server 2000 to 2003
Target Servers:
SLES 8 to 10 (OES)
Red Hat AS, 3 ES
33. Questions?
34. Implementation: Redesign the GroupWise® System Create the New Primary Domain
Link the old Primary to the New Primary
Convert the New Primary to Primary
Create the New Post Office Domain(s)
Link the New Domain(s) to the New Primary
Do NOT link to the old Domains, until its time to move users
Create the New Post Offices
Create the Gateway Domains
Create the Gateways
Create Test Users
Test the System
Move Mailboxes
35. Implementation: Move Users Mailboxes Why Move Users Mailboxes?
System–wide and Individual user Maintenance and clean up
Database Clean up
Broken, orphaned attachments and Trash left behind
Move User Formula: Size does matter!!
Estimates of User Mailbox Moves Assumptions
15 mins. Average per mailbox
10 mailboxes moved at the same time, to 20 mailboxes moved at the same time
1 person moving all mailboxes
Example Formula
400 mailboxes/20 mailboxes moved at 1 time =20 groups of mailboxes
20 groups x 15 mins. per group =300 mins.
300 mins./60mins. per hour =5hours.
36. Implementation: Move Users Mailboxes To Move Users –Preparation
Turn Off Virus Scanners
Unload GWAVA (/vsnoadm)
Contents Check with /attclip Support Option
Turn off Schedule Maintenance
Turn off QuickFinder
Verify/Clear no previous User Move Status from all domains perspective
Verify/Clear no pending operations
Verify Link Configuration between Source, Destination and Primary domain are 'Direct, TCP/IP'
Set POA Agent Settings
Message Handler Threads =10 to 20
TCP Handler Threads =10 to 20
Max Thread Usage for Priming and Moves =80/90
37. Implementation: Move Users Mailboxes To Move Users –Moving
Connect to Destination Domain
Select Source Post Office
Select User to move
Right Click –Move User
View Tools| GroupWise® Utilities| User Move Status
Set POA Logging to Verbose
View Source/Destination POA for Status and Item count
To Move Resources –Moving
Reassign all Resources to 'temp' user in old post office
Move Resources
Reassign Resources to a 'ResourceMgr' user in the new post office when asked
38. Implementation: Move Users Mailboxes F6 –Restart
Monitor the Source/Destination/Primary Domain MTA's
Problems Seen
Frequent Contacts
Password reset
Shared Folders
Visibility
Document Management
39. Real World Examples
40. Planning: Cluster and GroupWise® Design
41. Planning: Cluster and GroupWise® Design
42. Planning: Cluster and GroupWise® Design
43. Planning: Cluster and GroupWise® Design
44. Planning: Cluster and GroupWise® Design
45. Planning: Cluster and GroupWise® Design
46. Planning: Cluster and GroupWise® Design
47. Planning: Cluster and GroupWise® Design
48. Planning: Cluster and GroupWise® Design
49. Summary Review the Business Needs and Requirements
Seek Knowledge
Novell® Support Site, Forums, Cool Solutions, Books, Classes
Find Help
Consultants to fast–track
Evaluate the Costs involved
Plan the GroupWise® Redesign Process
Document a new GroupWise Design
Verify the Health of GroupWise
Move/Redesign/Build Domains and Post Offices
Move Users
Enjoy easier management and 99.999% uptime
50. Questions?
52. 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.