电子邮件服务器容量规划.ppt

Exchange电子邮件服务器容量规划 叶晓彬高级顾问微软顾问咨询部门 议题 容量规划过程Exchange服务器容量规划和设计基本监控总结 What sOutThere Benchmarks基准 不是容量规划最好的数据来源Why 单服务器不符合实际的配置单一的负荷压力没有额外的软件和冗余考虑用来对比服务器的类型 而不是提供容量规划的指南 其它方法 压力测试工具LoadSim2003 JetStress ESPSizingtoolsVaryinglevelsRiskofGIGOassolutiongrowsWhitepapersKBArticles技术顾问 系统架构师 6步容量规划的方法 获得基础数据充分理解SLA对于设计一个成功的项目非常重要建立自己的benchmarks获得基线数据确定瓶颈平衡系统资源实施 然后主动监控 获得数据 使用场景 Userprofiles转换为可计量的数据IOPS uMegacycles mailboxNetworkbytes mailbox利用峰值作容量规划 确定瓶颈 反应时间Server sreactiontoloadOnlypartofthepicture吞吐量Messages secTransactions sec瓶颈在哪里 High demandresourceWorkload dependentNeverreallyeliminate justmove 平衡系统资源 CPUMemoryPhysicalandVirtualI ODisksNetworkScaleuporscaleout 议题 容量规划过程Exchange服务器容量规划和设计服务器角色邮箱服务器容量规划I O规划工具基本监控总结 Exchange2003服务器角色 不同的角色不同的需求后端邮箱服务器前端服务器连接器InboundSMTPgateways SMTPBridgeheadX 400 legacyconnectorserversDLExpansionservers公共文件夹Free busy其它 e g OABGenerator 选择服务器 采用下面的服务器类型 BladeserversFEservers BEserverswithSAN iSCSIDenseserverHighlyavailable scalableBE FEserversHigh capacityserversBridgeheadservers replicatedsites departmentalVirtualserversLab hardware independentQA 考虑 PowerconsumptionDirect attachedversusnetworkstorageHigh performanceserversHigh availabilityoptions Exchange容量 CPU 最佳选择 仍然是4processorsFamily dependentYesterday PentiumIIIXeonToday Xeon XeonMP OpteronGoal Burn80 achallenge 扩展性的因素Hyperthreading dual coreClockfrequency 3 6GHz L2 L3cache upto8MBL3cache Front sidebus HyperTransportx64extensions 处理器比较 Time Frequency L3Cache FSBComparisons Front SideBus400MHz 533MHz ClockspeedboostwithoutL3cache AdditionofL3cache 1MB ClockspeedboostwithL3cache Platform ProLiantDL360G3 2P Exchange2003RTM identicalconfigurationWorkload 3 000MMB3 ResponseTimerelativelyconsistent Hyper ThreadingResults Platform ProLiantDL580G2 4P2 0GHz 2Mcache Exchange2003RTMWorkload MMB3 15 25 boost Exchange容量 内存 物理内存和虚拟内存4GBonhigh endback endservers 2 000mailboxesandabove 3GB BEandPFservers with 1GB其它减少虚拟内存碎片的方法HeapDecommitFreeBlockThresholdWatchFreeSystemPageTableEntries USERVA 3030ESECachetuning不要在FE SMTP上配置CheckKBs815372 810371 Exchange容量 网络 后端服务器Typically 100MbitfullduplexsufficientConsiderGigabitandNICteamingif Networkbackup restoreiSCSIorNASstorage TCPOffloadEnginesupportHighconcentrationofOWA POP IMAPusersConsiderNICswithIPSecoffloadMAPIcompression bufferpacking30 40 improvementincachedmodesynchronization standardMAPItrafficoverE2K前端服务器Dualswitched100MbitorGbitdefault Exchange容量 网络基本考虑点 SizeforI O and capacity考虑SLAArchitectforhighavailability backup don t add on VSSorreplication将数据库和log分放在不同的PerformanceanddisasterrecoveryconsiderationsRAID10everywhere优化延迟Database fastreads 20ms Logs fastwrites 10ms BurstyrandomI OpatternsDesignforcontrollercacheavoidanceDesignforMondaymorningpeak DiskIOPs IOper spindledependenciesRAIDtypeLatencyrequirementsAccesspatternRead writemixSpindleperformance rotationalspeed 基本原则 FCandU320SCSI 10Kdisks 120IOPSperdisk 20ms15Kdisks 160IOPSperdisk 20msConservativeuseof100IOPSperdiskfordesignallowsroomforpeakperiodsFigureareRAID1 0 RAID5IOPSdropsto 90 10KdiskTransactionlogsrequire 10 ofSGIOPS 磁盘瓶颈分析 MSA1000 16disks database 1DB LUN RAID0 1Array increasingloadtosaturationgeneratedbyJetStress 20ms write 10ms read 存储设计 前端服务器 SMTPCreateasinglepartition 30smallmsgs sec spindleRAID0 1recommended 100 write backcacheX 400andlegacyconnectorsSeparateMTA RAID5 logs RAID1 andpagefile ifpossibleOtherFEserversNotI O intensive 存储设计 后端服务器 很多需要考虑的因素 Array LUNdesignJournaling ArchivingVSS basedplexes snapshot clones Temp TMPdrivePartitionAlignmentwithphysicalsectors Diskpar DiskpartwithSP1 tomentionafew DatabaseIOPs uRates Roughestimates MAPIcorporateusers ISP light user 3IOPs uCorporate 7 1 2IOPs uMicrosoft 9 3IOPs uRatesdonotstayconstantasload mailboxsizesincrease RAID级别比较 34disksfordatabasesOnelargeRAID1 0setMostly3 diskRAID5setsMostly4 diskRAID6 ADG sets RAID5performancebestwithmultiplesmallR5sets StoragePlanningCalculatorforExchange ControllerCacheMix RAID1 0Controller specific50 50bestSomewrite cachenecessaryRAID5100 writeisbestWritegatheringbenefitsRead aheaddetrimentaltorandomworkloadWatermarksettingrecommendedat80 HBA优化 Queuedepthisarray anddeployment specificValuesforanHPEVA5000 EmulexHBAsEmulexHBAparameterBaselineModQueueTarget10HKEY LOCAL MACHINE SYSTEM CurrentControlSet Services lpxnds Parameters Device0 NumberofRequests50150HKEY LOCAL MACHINE SYSTEM CurrentControlSet Services lpxnds Parameters Device NAS和iSCSI存储 NAS定位在中小企业或者部门级应用经测试的场景Low to250 Medium to750 High to1 500iSCSITestedScenariosforWindowsStorageServersLow testedto500MediumtoHigh testedto5 000Expansionstoragee g augmentingFibreChannelRecoveryStorageGroupPublicFolderServerArchiving ILM InformationLifecycleManagement 提高iSCSI性能 取决于瓶颈在哪里 Startwith speedofspindles TeamedGigEcanhandleupwardsof8 500IOPSApprox 7010Kor 5015KdisksBottleneckedatTargetDiskperformance e g move10K 15KorATA SCSI To fromtargets Increasebandwidth esp backups IsolateGigEnetworkNICTeamingAdditionalNICsJumboFrames BottleneckedatInitiatoriSCSIHBA andTCPOffloadEngine insteadofsoft Exchange容量 软件 影响CPU或者其它资源的软件组件防病毒软件 防垃圾软件存档 日志备份Exchange功能创建OAB内容索引其它业务应用MobiledevicesupportE g 1BlackBerryuser impactof2 21MAPIusers CPU storageandnetwork onExchangeBEserver basedonlabtestingofBES3 5 软件影响的示例 Referenceconfigurationincludedmanagement backupagentsAVsolutionutilizedSTOREAVAPI 公共文件夹 如果使用频繁 需要专用的公共文件夹服务数目有限的大型的PF服务器要优于很多小型的PF服务器减少备份恢复时间 减少复制流量管理和维护成本深层次PF结构比平板结构的要扩展性好复制对于不同的权限的处理能力客户端操作 sort search expand 影响更小Hotfixtoaddressexistingdeephierarchieswithdifferentpermissionsatvariousnodesinthetree 公共文件夹容量规划 Maximum250subfolders folderConsiderACLschema arrangebasedonusersetsthatgainaccesstoparentfolderMaximum10Kitems folderConfigureexpirationaccordingly orsegmentingintosub topicsMaximum10Kusers PFdatabaseVMissuesLabtests STORE 2 2GBvirtualbytesinclusteredenvironmentwithnoactivemailusersMonitorMSExchangeISPublic ClientLogonsandPeakClientLogonsAssume1 6xscalingfactor and1 2R Wmix ActiveDirectory容量规划 Typicalconfiguration2P 2GB RAID10forDIT RAID1forlogsDependsonreplication typeofdeploymentThirdpartyADappswillimpactUse 3GBonGCwith 1GBRAMLargerESECachemeans20 40 diskI OdecreaseDedicatedADsiteforExchangeHowmanyclientsperGlobalCatalogServer 1 4GC ExchangeprocessorratioGCco locatedwithmailboxserversLogintimes DGdecomposition DelegateaccessGCwithlargeuserpopulations4 000clientsperGCUseClosestGCregistrykeyforOutlook2003clients MaintenanceConsiderations ISOnlineMaintenanceCheckingActiveDirectoryfordeletedmailboxesMinimalBEserverimpactSchedulingimportanttominimizeADimpactDisk intensivemaintenanceactivitiesPermanentlyremovemailboxes messagesolderthanretentionpolicyOnlinedefragStaggerintervalswithbackupschedulePFOnlineMaintenanceAllowfor4hours day andfullonlinemaintenanceweekly 议题 容量规划过程Exchange服务器容量规划和设计基本监控主要的对象和计数器总结 基线数据分析 性能计数器分析细致考察趋势分析帮助你进行主动性的容量管理95thpercentileinsteadofaverage采样 采样 采样 性能对象和计数器最小集 协议和邮箱计数器 磁盘计数器 内存计数器 Topics 容量规划过程Exchange服务器容量规划和设计基本监控总结 总结 Benchmarking Caveatemptor Developowntests baselines acceptancecriteria 基本规则Exchange大多数情况下自我调整分隔角色以更好的支持用户邮箱服务器CPU 2 4 ConsiderfastestFSB largerL3cacheoverCPUspeed Memory 4GBNetwork 100Mbit dual100MbitforFEActiveDirectory1GCneareachExchangeserverand4 000users为周一早晨作容量规划 并且考虑快速恢复的SLA要求在生产环境中恢复一个数据库 存储总结 数据库 采用很多磁盘Cachemisses smallrandomI Otothedisks 70 30read writeratio 60 40forsizingTransactionlogging 快速写能力SmallsequentialI Otothelogs增加I Opersecond增加更多 更快的磁盘改变RAID级别 from5to1 减少延迟 ms 优化HBAs 资源 其它资源 2005MicrosoftCorporation Allrightsreserved Thispresentationisforinformationalpurposesonly Microsoftmakesnowarranties expressorimplied inthissummary StorageSizingExercise BackoftheNapkin Threescenarios4 000 medium users8 000 light users4 000 heavier usersBaselineassumptionsBaselinedisk 72 8GBdisk 66GBuseablestorage10Kspindle 120randomIOPS15Kspindle 150randomIOPS 0 8IOPSaverage 1 0IOPSpeak4 000users 1 0IOPS 4 000IOPS3 1ratio 3 000readand1 000writeIOPSBackenddiskIOPS RAID10calculationTotalIOPS 3 000 2 1 000 5 00042drives 10KRPMor34drives 15KBackenddiskIOPS RAID5calculationTotalIOPS 3 000 4 1 000 7 00059drives 10Kor47drives 15K 200MBmailboxes4 000users 200MB 1 5 flufffactor fordeleteditems maintenance etc 1 172GB1 172GB 66GB drive 18drivesBackenddisks RAID10calculation18drives 2 RAID10 36drivesBestmatchto36drives73GB 15KRPM capacity Backenddisks RAID5calculation18drives 1 2 RAID5 22drivesPoormatchto59 10K or47 15K IOPS BackoftheNapkin4 000 medium users Capacity 0 3IOPSaverage 0 5IOPSpeak8 000users 0 5IOPS 4 000IOPS3 1ratio 3 000readand1 000writeIOPSBackenddiskIOPS RAID10calculationTotalIOPS 3 000 2 1 000 5 00042drives 10KRPMor34drives 15KBackenddiskIOPS RAID5calculationTotalIOPS 3 000 4 1 000 7 00059drives 10Kor47drives 15K 200MBmailboxes8 000users 200MB 1 5 2 344GB2 344GB 66GB drive 36drivesBackenddisks RAID10calculation36drives 2 RAID10 72drives 73GBWouldmatch36drives146GB 15KRPMor42drives146GB 10KRPM I O Backenddisks RAID5calculation36drives 1 2 RAID5 44drives 73GBWouldmatch