虚拟化Exchange 2010之最佳实践.docx

很久没有发有营养的东西了，现在再来挖一个坑，希望在Exchange 2010发布之前能填完。本篇的题目为虚拟化Exchange 2010之最佳实践，着重讲解在使用 vSphere 或Hyper-V 虚拟化Exchange 2010时需要注意的事项。解释不会很详细，不理解的请自行体会或者查阅相关文档。列下目录先: Active Directory Operating System: Windows 2008 Networking Fibre Channel Array Virtualization Scripting( used to quickly configure parts of the solution ) Replication Disaster Recovery Archiving Journaling Storage Design Microsoft Storage Calc EMC Storage Calc 1 database/drive ( DAG replication ) Raid5 Raid6 Raid10 Raid1 Platform Specific Best Practices第一节：活动目录的最佳实践1. 对于每AD站点,最低配置为两DC/GC。2. DC之间能够相互自动容灾，但是要确保DC之间的相互复制成功。3. 跟据微软的最佳实践来安排服务器角色。如果有多于两台服务器，可以考虑把PDC Emulator 分立开来。另外，Schema master和domain naming master 角色应该被放在同一个DC上，因为这两个角色一般不太用（没什么负载），但是却很敏感，需要特别保护。/kb/2168994. 虚拟化DC时要确保不要对DC做任何snapshot。原因是如果使用snapshot 回到过去的状态，此DC将很有可能不能再正常复制。详细见微软KB.5. 虽说虚拟化系统的稳定性还是很有保证的，但是在多台DC之中，最好保证有一台物理机，以确保在磁盘组断电或者维护时，还能有一台DC临时顶顶。第二节：系统配置的最佳实践1. 修改page文件设置缺省情况下，Windows 2008 会把page 文件放在任意连接的存储上，有可能不巧就放在Exchange的存储上。为了避免这个问题，需要把Automattically manage paging file for all drives 勾去掉，并且人为地设置好系统的page文件的路径和大小。对于内存大于8GB的服务器，一般推荐page文件的大小一般为内存的大小加10mb, 最大可设置为内存的1.5倍。2. 禁止休眠功能使用下列命令禁止服务器休眠功能:powercfg h off你还可以把服务器的 power profile改成high performance, 然后进入advanced 选线，把SleepHibernation 改成Never.修改好以后，记得重启。重启后，在系统盘上，不应该看见那个隐藏的文件 hiberfil.sys。不过有些时候，可能不会自动删除，你可能需要手工去删掉。3. 关于时间同步时间同步对于服务器来说至关重要。时间不同步可能导致用户无法登陆，服务无法启动，或者数据损坏等问题。在虚拟机中，我们可以使用VMtools 或者W32Time 来同步时间。但是需要注意，两者不可以同时使用，否则可能会造成意想不到的问题！A. 如果使用windows的缺省同步方式(W32Time), 记得把VMTools里面同步时间的选项去掉，另外，还需要为PDC emulator 配置一个NTP来源(master time server)，这个服务器一般来说是内部某个Unix 服务器，然后这个Unix服务器再和外面某共用服务器同步（比如NASA的时间服务器）。需要修改注册表如下:HKLMSystemCurrentControlSetServicesW32TimeParametersChange TypeREG_SZ value from NT5DS to NTPChange NtpServer value ,0x1to an external stratum 1 time source, ,0x1HKLMSystemCurrentControlSetServicesW32TimeConfigChange AnnounceFlagsREG_DWORD from 10 to 5改完后重启时间服务（time service) net stop w32time & net start w32time然后人为的强行更新一次w32tm /resync /rediscoverB. 如果使用VMtools同步时间，需要在PDC Emulator上修改域控制器策略，把W32Time的时间同步先停了。然后确认虚拟机上的时间同步选项打开了。最后在 VMware Client里连接到ESX服务器上去配置好时间同步，方法类似前面。C.最后闲扯一句，对于Linux的虚机（版本低于2.6.18时)，由于一些bug, 虚机的时钟会跑得不对，记得一定要用时间同步。第三节：网络配置的最佳实践配置iSCSI存储的最佳实践: Recommended using 1Gbps NICs iSCSI HBA are not taboo, just expensive Disable Microsoft File and Print sharing Disable Microsoft Networks Disable All TCP Offload Engine parameters These can vary depending on the manufacturer of the NIC. IOAT ( Intel (r) IO Acceloration Technology ) bios enable Windows requires driver installed via Intel Site Enables Receive Side Scaling on the NIC configuration parameters Causes each nic to use specific processors (affinity) Disable,iSCSI traffic can overwhelm the single processor.This setting willallow iSCSI traffic to be handled by all available processors. DAG replication iSCSI Networks/Subnets may get added in during DAG network creation. Remove from DAG networks, they should not participate. VLAN: Use VLANs to segment iSCSI traffic if in use on production networks. Seperate iSCSI traffic from production network.iSCSI is very network intensive and can/will affect production networks. MPIO/MCS MPIO should be used with CLARiiON CX/AX arrays EMCPowerPath or Microsoft MPIO 2008 can be used for multipathing. MCS (multiple connections session) Celerra arrays require MCS configuration for connectivity to these arrays. MultipleiSCSI networks: It is recommended to use at least 2 Network cardsdedicated for iSCSI.This builds in fault tolerance and increasesperformance. Multiple Switches/VLAN: Multiples switches are preferred (independant networks) for fault tolerance and performance. VLAN can be used if multiple switches cannot. Microsoft Initiator - Windows 2008 now comes with the Initiator built into the product.No additional install required. Navisphere is required to be installed for CLARiiON registration. AUTO/AUTO:Although auto/auto makes administration considerably simpler, it isrecommended to statically set NICs to 1000 or 1Gbps (hardware vendordepending).Additionally the Switch and Array also should bestatically set to match this configuration. NOTE:CAT5/CAT5e: If cat5 or cat5e (which is rated for 1Gbps) willintermitantly fail or not work at all when static configuration oftransmit rate is hard coded to 1Gpbs.)If the customer is not sure,upon setting of the NIC to 1000/1Gbps the network immediately showsunplugged they have one of these cables. CAT6: CAT6 is ratedand will work 100% at 1Gbps.For all iSCSI if the customer wishes toget full performance should upgrade to CAT6 Ethernet cables. JumboFrames does increase performance, but also increases administration andtime to resolution during performance issues.Many customers haveproblems with network MTU sizes.This change increases the MTU size to9,000 or 16,000.EMC CLARiiONs and Celerras do accept this size. Newer switches will vary from 9 or 16, check technical overview ofswitch to be sure.This setting must match end to end to work.Whenin doubt DONT USE THIS FEATURE. Guest/Child configurations: VMwareGuests OS and Hyper-V Child OS configuration of iSCSI is the same asphysical.Dedicate Network Adapters for iSCSI traffic and configurethe virtual machine to have dedicated access to these adapters. Presentation and configuration, and Best Practices will be the same. MultipleGuests / iSCSI network card.This can be done, and has shown toimprove utilization of iSCSI network cards.Careful monitoring must bedone to insure Exchange Latencies do not exceed recommended MicrosoftMaximums. Host/Guest Automatic Power Off of Network Card should be disabled. TCPAckFrequency=1 for all iSCSI adapters.Refer to the following KB /kb/328890 KeepAliveTime Hive:HKEY_LOCAL_MACHINEKey:SYSTEMCurrentControlSetServicesTcpipParametersName:KeepAliveTimeType:REG_DWORDValue:300,000配置DAG 相关网络的最佳实践:1. It is recommended to have seperatededicated networks for Production and DAG Replication traffic. Namingyour Network Adapters to match the functions can aide whenidentification during DAG