Hardware Sizing Seminar

1

• Hardware Sizing Seminar

March 07, 2005 OMB, Singapore
2

• Hardware Sizing Seminar

Danny Condecido MCT, MCSA, MCSE, MCDBA
Partner Technology Specialist Microsoft Business
Solutions
March 07, 2005 OMB, Singapore
3
Part 1 Agenda

• Hardware Sizing Steps
• MBS Products Architecture
• Navision
• Axapta
• Great Plains
• MS CRM
• Storage Subsystems Architecture
• Network Subsystems
• Processor and Memory Subsystems
• Terminal Server Environment

4
Hardware Sizing Steps

• Knowing your Application Architecture
• Do a proper scoping
• Develop your Deployment Scenario
• Use Sizing Data Gathering Tools
• Consider other Factors i.e., Future Growth,
  Organization Restructures, etc.
  
• Derive your Bill of Materials (BOM)

5
Sizing Considerations
No. of Records
Response Time
P E R F O R M A N C E
6
MBS Product Architectures

• Axapta
• Great Plains
• Navision
• MS CRM

7
Microsoft Axapta Architecture
8
Axapta System Components

• Client
• Axapta Object Server (AOS)
• Database Server
• Batch Server
• IIS (Web) Server

9
Microsoft Axapta Architecture 2Tier Basic
Configuration
10
Microsoft Axapta Architecture 3Tier Rich
Configuration
11
Microsoft Axapta Architecture 3Tier Thin
Configuration
12
Microsoft Axapta Web IIS, Deployment COM

• Advantages
• Easy deployment just the browser
• Disadvantages
• Only browser functionality
• No windows 32 functionality e.g. Office
  integration
  

13
Microsoft Axapta AOS Cluster

• AOS Cluster

14
Axapta Batch Server

• Batch Server
• Problem
• Client PCs are typically not new thus slow
• Response time grows exponentially with users
• Solution
• Use fast batch server
• CPU speed grows factor of 2 per 18 months
• Example
• Clients invoicing journals
• 3 year old client against new batch server
• Fast CPU means shorter lock time thus slower
  growth

15
Great Plains Architecture
16
Great Plains - Minimum Hardware Solution

• Use only Financial series modules (GL, BR, PM,
  FA)
  
• Have between 0 and 15 concurrent users
• Use Report Writer, some Crystal Reports, and FRx
• Having no more than 500 transactions total per
  day
  
• Very little importing or none at all

17
Great Plains - Midrange Hardware Solution

• Uses Terminal Server
• Use of Report Writer, Crystal Reports and FRx
• Having no more than 2,000 transactions total per
  day originating in Sales, Payables or General
  Ledger
  
• Uses some type of Import routine
• Dedicated SQL Server Only

18
Great Plains - High-End Hardware Solution

• Uses Terminal Server/Metaframe
• Use of Report Writer, Crystal Reports and FRx
  heavily
  
• Having no more than 5,000 transactions total per
  day originating in Sales, Payables or General
  Ledger
  
• Heavy use of some type of Import routine
• Dedicated SQL Server Only

19
Great Plains-Enterprise Hardware Solution

• Perform OLAP (online analytical processing) cube
  generation (to different machine)
  
• Large daily transaction volumes
• General Ledger Posting 200,000 distributions
• Payables Posting 10,000 vouchers
• Receivables 10,000 Invoice/Cash Receipt
• Sales Order 10,000 Invoice posting
• Payroll 50,000 checks (calculate and build)
• Heavy use of some type of Import routine
• Dedicated SQL Server Only

20
Microsoft CRM 1.2 Architecture
21
MS CRM System Components
Active Directory /DNS
Exchange Server (Email Router)
MS CRM Server
SQL Server
SFOC
22
MS CRM-Single Server deployment

• Small Business Server deployment
• Small Business Server
• Users up to 25 recommended 40 supported

MS CRM Server
SQL Server
SFOC
Active Directory /DNS
Exchange Server (Email Router)
23
MS CRM-Medium deployment

• Three Box deployment
• MS CRM and SQL Server 2000
• AD Domain Controller
• Exchange Server 2000/2003
• Users up to 50 recommended 100 supported

Active Directory /DNS
SFOC
MS CRM Server
SQL Server
Exchange Server (Email Router)
24
MS CRM-Large deployment

• Four Box (or More) deployment
• Minimum Four Dedicated Servers
• Users up to 150 recommended 300 supported

Active Directory /DNS
Exchange Server (Email Router)
MS CRM Server
SQL Server
25
Microsoft Navision Architecture

• Navision Technology Framework
• 2-Tier Architecture
• Terminal Services Environment
• N-Tier Architecture

26
Navision Technology Framework
Employee
Efficiency
WIN32
User Portal
ApplicationServer
Collaboration
BusinessPartner
Commerce Gateway
BizTalk Server
Openness
Commerce Portal
Microsoft Navision DatabaseServer / SQL Server
Commerce Server
Client
Reliability
Business Logic
Database
Adaptability
Report
Form
Code Unit
Dataport
Table
27
Navision Architecture 2-Tier

• Microsoft Navision is a two-tier solution
  application.
  
• It consists of a Database Management System
  (DBMS) that resides on the server and a Graphical
  User Interface (GUI) that resides on the client.
  
• You can also configure the client to be a
  stand-alone installation, which means that the
  client functions as a server and a single client
  in one.

28
Navision Architecture N-Tier

• The Navision Application Server (NAS) is a
  middle-tier server that supports an n-tier
  architecture, which executes business logic
  without user intervention.
• Microsoft Navision Application Server allows you
  to communicate with external services.
  
• Microsoft Navision Application Server acts as a
  client towards a database server and can act as a
  server for other services.
  
• Microsoft Navision Application Server can
  communicate with both Microsoft Navision Database
  Server and the SQL Server Option in the same way
  as a Microsoft Navision client.

29
Storage Subsystems

• What is Redundant Array of Independent Disks
  (RAID)?
  
• Hardware RAID vs. Software RAID?
• How to measure database growth?

30
Storage Subsystems - RAID 0

• RAID 0 Striping
• Simple striping of data across disks in the
  array
  
• No RAID resilience - if one disk fails, then
  the entire array fails
  
• Good for load balancing elimination of hot
  spindles
  
• Array capacity the number of disks in the
  array
  

31
Storage Subsystems - RAID 1

• RAID 1 Mirroring
• Mirroring, shadowing, duplexing for resilience
  with second copy of data
  
• Can enable simultaneous reads on both parts of
  mirror
  
• Array capacity the number of disks in the RAID
  1 set divided by two (or three for triple
  mirroring)
  

32
Storage Subsystems - RAID 5

• RAID 5 Rotating Parity
• Data striping with ECC- based disk redundancy
• All disks have round-robin share of ECC data
• Good small block read I/O performance but complex
  write process
  
• Array Capacity the number of disks in the array
  minus one
  

33
Storage Subsystems - RAID 01

• RAID 01
• Inherits the increased data availability from
  RAID 1
  
• And, the increased read performance from RAID 0

34
Disk Layout on SQL database
RAID 0
Large Deployment
Disk 1
Disk 2
Temp DB
RAID 1
SQL Trans. Log
Disk 3
Disk 5
Disk 4
Disk 6
RAID 5 or RAID 01
Disk 7
Disk 8
Disk 9
Disk 10
SQL Database files
Disk 11
Disk 12
Disk 13
Disk 14
35
Disk Layout on Native database for Navision
Raid 1
Navision Database .fdb
Disk 1
Disk 2
36
Using Database Sizing Tool

• DEMO

https//mbs.microsoft.com/partnersource/products/n
avision/documentation/benchmarks/NavisionSQLResour
ceKit.htm
37
Processor and Memory Subsystems

• Does it matter?
• Single or Multiple Processors?
• How much RAM should I use or buy?

38
Terminal Services

• When do I use Terminal Service Environment?
• Microsoft TS or MetaFrame (Citrix)?
• What hardware metrics to follow in sizing TS?

39
Windows Terminal Server

• Windows Terminal Server provides remote access to
  a server desktop through "thin client" software,
  serving as a terminal emulator.
  

40
Terminal Services Environment

• Terminal Services in Windows 2000 and 2003 offer
  the low cost, centrally managed environment.
  
• Terminal Services in Windows 2000 and 2003 works
  by running the application on the central server
  system and only lets the client control the
  application (similar to remote control) and
  receives the output displayed at the client
  window.
• This reduces the bandwidth needed between the
  Windows client and the corporate ERP, but does
  not give any means of exploiting the Windows
  client capacity with respect to processing.
• Also important is the amount of concurrent
  clients Terminal Services for Windows can handle
  on any given hardware.
  

41
Terminal Services Hardware Configuration

• Memory Subsystems
• 20MB of RAM per user (Typical Knowledge Worker
  Scenario)
  
• Network Subsystems
• Consider using two network adapters, dedicating
  one to RDP traffic only
  
• It can be used with a dial-up connectivity
  (56Kbps) with longer latency as compared to Local
  Area Network
  
• If network performance metrics are unknown, HP
  suggests 20kbps as a starting point for the
  network consumption per user for ICA and RDP
  clients.
• Storage Subsystems
• 2 x 18.2GB Ultra3 SCSI _at_ RAID1 for Operating
  System Applications
  
• 2 x 9.1GB Ultra3 SCSI _at_ RAID1 for Page File
• If terminal services is running on server-class
  hardware, use hardware RAID

42
Network Subsystems

• What is bandwidth?
• When is a specific Bandwidth slow?
• Can I use dial-up connectivity?
• How about VPN, is it a viable solution?

43
Network Sizing

• Compare bandwidth to a highway.  The more lanes a
  highway has the more bandwidth is available for
  the cars to travel.
  
• Latency is the speed at which the cars can travel
  on the highway.  As more cars collect on the
  highway they have to travel at a slower speed..
  

• DEMO

44
Thin Client (TS) Minimum and Acceptable Areas
This figures may be applied also to your VPN
implementation.
45
Tea Break

• 15 Minutes

46
Part 2 Agenda

• Deployment Scenarios
• Bill of Materials
• Q A

47
Axapta Deployment Scenariosand Bill of
Materials (BOM)
48
Axapta Hardware Requirements

• Microsoft Axapta Sizing
• Microsoft Axapta Sizing Database
• Microsoft Axapta Sizing Storage Systems
• Recommended Hardware for Axapta AOS
• Recommended Hardware for Axapta Application File
  Server
  
• Recommended Hardware for Axapta Rich Clients
• Recommended Hardware for Axapta Thin Clients

49
Microsoft Axapta Sizing

• Axapta Standard User (ASU)
• 1 ASU is the load generated by Microsoft Axapta
  3.0 when creating and invoicing the amount of 10
  sales orders, with 5 order lines each, processed
  over one hour. This is a total of 10 Sales
  orders, with a total of 50 sales lines in one
  hour.
• Official Hardware sizing guides
• PartnerSource https//mbs.microsoft.com/partnerso
  urce/products/axapta/documentation/benchmarks/Axap
  taSizingGuide.htm

50
Microsoft Axapta Sizing - Database

• Database Server
• More than 400 ASU, contact Microsoft Business
  Solutions
  

51
Recommended Hardware for Axapta AOS

• Axapta Object Server (AOS)-AOS is the Application
  Server part of the 3-tier client/server
  Enterprise version of Microsoft Axapta

52
Recommended Hardware for Axapta Application File
Server

• Application File Server
• To provide access to the application files to one
  or more AOS and 2tier clients.
  
• The CPU and Memory requirements are minimal
  essentially what the operating system requires.
  
• Commonly uses an existing File Server to host the
  application files.
  

53
Recommended Hardware for Axapta Rich Clients

• Microsoft Axapta Client Requirements
• 2-Tier / 3-Tier Rich

54
Recommended Hardware for Axapta Thin Clients

• Microsoft Axapta Client Requirements
• 3-Tier Thin

55
Axapta 3.0 HP Sizing Guideline

• Sizing guideline for Axapta is based on users
  count and DISA (Dynamic Internet Solution
  Architecture) configuration
  
• Entry Level DISA configuration (
• Medium Level DISA configuration (51-500 users)
• Enterprise Level DISA configuration (501-2000
  users)

56
Axapta 3.0 Entry Level Hardware Configuration
ML Servers
DL Servers
HP ProCurve 10/100 Ethernet Switch
HP ProCurve 10/100 Ethernet Switch
ML330 G2
DL380 G4
AOS Servers
AOS Server
HP ProCurve 10/100 Ethernet Switch
HP ProCurve 10/100 Ethernet Switch
ML330 G2
DL380 G4
Database Server
Database Server
57
Axapta 3.0 Entry Level Hardware BOM based on DL
and ML servers
DL Server
ML Server
58
Axapta 3.0 Medium Level Hardware Configuration
51-500 clients
51-500 clients
HP ProCurve 10/100 Ethernet Switch
HP ProCurve 10/100 Ethernet Switch
ML330 G2
DL380 G4
(2-5) AOS Servers
(2-5) AOS Servers
HP ProCurve 10/100 Ethernet Switch
HP ProCurve 10/100 Ethernet Switch
DL580
DL580
Database Server
Database Server
NOTE More than 200 users, Technical Presales
AdvisoryGroup TPAG approval is required.
59
Axapta 3.0 Medium Level Hardware BOM based on ML
and DL servers
60
Axapta 3.0 Hardware Configuration based on Blades
61
Axapta 3.0 Enterprise Level Hardware Configuration
ML Profile
51-500 clients
DL Profile
HP ProCurve 10/100 Ethernet Switch
DL380 G4
(2-5) AOS Servers
HP ProCurve 10/100 Ethernet Switch
DL580
Database Server
NOTE More than 200 users, Technical Presales
AdvisoryGroup TPAG approval is required.
62
Axapta 3.0 Hardware BOM for Enterprise Type
Deployment
DL Servers
Blade Servers
63
Great Plains Deployment Scenariosand Bill of
Materials (BOM)
64
Minimum Hardware Solution
65
Great Plains-Minimum Server Requirements

• Minimum Server Requirements
• DL380 G4 3.2 GHz
• 1 GB RAM
• 2 x 36 GB(R1) for OS and SQL Application
• 3 x 72 GB (R5) for Database log and data files
• Integrated SA 6i controller
• Integrated 10/100/1000 Mbps Ethernet

66
Great Plains-Midrange Hardware Solution
67
Great Plains-Midrange Server Requirements

• DL580 G2 2 x 2.7 GHz
• 2 GB RAM
• Integrated SA 6i Controller
• Smart Array 6402 Controller Card for MSA30
• 2 x 36GB(R1) for OS and SQL Application
• 2 x 36GB(R1) for Database log
• 4 x 72GB(R5) for Data files
• 2x 36GB (R1) for TempDB
• 2 x36 GB(R0) for SQL Backup
• 1 x MSA30 external storage enclosure

68
Great Plains - High-End Hardware Solution
69
Great Plains High-End Server Requirements

• DL740 4 x 2.7 GHz
• 4 GB RAM
• Integrated SA 6i Controller
• Smart Array 6402 Controller
• 2 x 36GB(R1) for OS and SQL Application
• 4 x 36GB(R1) for Database log
• 8 x 72GB(ADG) for Data files
• 4 x 36GB (R1) for TempDB
• 2 x 36GB(R0) for SQL Backup
• 2 x MSA30 external storage enclosure

70
Enterprise Hardware Solution
71
MS CRM Deployment Scenariosand Bill of
Materials (BOM)
72
Single Server deployment

Recommended Hardware Requirements

Processor Dual 1.8 GHz Xeon P4

RAM 1 GB

Controller SCSI (second controller preferred)
with Hardware RAID 5 (3 drives for RAID 5 2
drives for RAID 1) Network Card 100/1000 Mbps

MS CRM Server
SQL Server
Active Directory /DNS
Exchange Server (Email Router)
SFOC
73
Microsoft CRM Sample Sizing configuration for 100 concurrent users
74
Medium deployment

CRM Server Recommended Hardware Requirements

Processor Dual 1.8 GHz Xeon P4

RAM 1 GB

Controller SCSI (second controller preferred)
with Hardware RAID 5 (3 drives for RAID 5 -2
RAID 1)

Network Card 100/1000 Mbps

Active Directory /DNS
MS CRM Server
SQL Server
SFOC
Exchange Server (Email Router)
75
Microsoft CRM Sample Sizing Configuration for 200 concurrent users
76
Large deployment

CRM Server (s) and SQL Server Recommended
Hardware Requirements

Processor Dual 1.8 GHz Xeon P4

RAM 1 GB

Controller SCSI (second controller preferred)
with Hardware RAID 5

(3 drives for RAID 5 -2 RAID 1)

Network Card 100/1000 Mbps

Active Directory /DNS
Exchange Server (Email Router)
NOTE 100 Sales for Outlook Users
500 Web Client Users Citrix/Terminal Solution R
equired Multilingual/Multicurrency Required, Te
chnical Presales Advisory Group TPAG analysis
and approval is required.
MS CRM Server
SQL Server
77
Microsoft CRM Sample Sizing Configuration for 500 concurrent users
78
Sales For Outlook Client (SFOC) Hardware
Recommendation

• CRM Client Recommended Hardware Requirements
• Processor P4 / 500 MHz
• RAM 512 MB
• Hard Disk 100 MB Free Space (At least)
• Network Card 100/1000 Mbps

Synchronization
SFOC/MSDE
MS CRM Server
SQL Server
Office XP / Office 2003
Windows XP SP2
79
Navision Deployment Scenariosand Bill of
Materials (BOM)
80
Microsoft Navision Hardware Profiles

• Profile 1
• Up to 75 users, used profile 1 (2-way system)
• Profile 2
• Above 75 to 100 users, used profile 2 (4-way
  system)

81
Navision Hardware Architecture Diagram
PROFILE 1 Up to 75 users
PROFILE 2 Up to 100 users
82
Hardware listing for Navision Profile 1 using
2-way server

• Hardware Server Requirements
• DL380 G4 3.2 GHz
• 2 GB RAM
• 2 x 36 GB(R1) for OS and Application
• 8 x 72 GB (R5) for Database
• 4 x 72 GB (R1) for log file
• Integrated SA 6i controller
• Smart Array 6402 Controller Card for MSA30
• Integrated 10/100/1000 Mbps Ethernet
• MSA30 external SCSI based Storage Enclosure

83
Hardware and Software listing for Navision
Profile 2 using 4-way server

• Hardware Server Requirements
• DL580 G2 4 x 3.0 GHz
• 8 GB RAM
• Integrated SA 6i Controller
• FC Host Adapter for MSA1000
• 2 x 36GB(R1) for OS and Application
• 8 x 72GB(R5) for Database
• 4 x 72GB(R1) for Data Log file
• 1 x MSA1000 external Fibre-channel storage
  enclosure

84
Conclusion
85
Questions???