VMware虚拟化最佳实践及规划

虚拟化最佳实践及规划议程应用实施范围考虑服务器采购考虑虚拟机部署考虑管理维护考虑议程应用实施范围考虑服务器采购考虑虚拟机部署考虑管理维护考虑应用实施范围总体原则不适合采用虚拟化的应用具有特殊硬件访问要求的应用高性能图形显卡

不适用虚拟化

特殊的串/并行加密设备不适用虚拟化USB设备连接需求

可能不适用，可采用外置USB设备代替，需经过测试即使在高配置的服务器上仍然具有很高负载的应用

可能不适用，需分析当前服务器配置情况可以采用虚拟化的应用除上述不适合采用虚拟化的应用之外的所有应用可根据应用迁移的复杂程度决定虚拟化先后顺序较易实现P2V的应用可先做迁移，如可用Converter工具直接迁移的应用较难或不能做P2V迁移的应用可考虑采用重新安装方式后迁根据管理的需要决定是否做虚拟化虚拟化转变过程对现有业务的影响程度转变为虚拟化后对现有管理的影响程度部门之间协调的难易程度虚拟化宿主服务器的部署类型垂直扩展与水平扩展部署模式不同资源池的“量子化”模型物理主机HypervisorVMOSAppVMOSAppVMOSAppVMOSAppVMOSAppVMOSAppVMOSAppVMOSAppVMOSAppPhysicalHostHypervisorVMOSAppVMOSAppVMOSAppPhysicalHostHypervisorVMOSAppVMOSAppVMOSApp物理主机HypervisorVMOSAppVMOSAppVMOSApp不同资源池的类型垂直扩展的主机模式提供更大的连续性资源空间更容易满足不同负载的吻合性要求可提供更高的资源利用率水平扩展的集群主机模式更像是一组小池子的集合多组小容量资源池需要更多的监控管理模块化使用既有优点也有缺点影响虚拟化部署的参数体系功能的多样化服务器的重要性独立服务器不重要重要(独立的,本地存储等等)(群集的,多主机的等等)服务器农场(水平扩展服务器群集，公用服务器等等)(后端办公,本地应用等等)负载约束技术约束商业约束困难度增加负载约束不同的资源组都需要分别考虑CPU利用率磁盘I/O网络I/O内存利用率虚拟化造成的额外负载通常也要做一定考虑，如磁盘和网络的I/O会增加CPU的负担iSCSI存储访问也会增加CPU负担运维的周期性负载变化也必须考虑进来月末负载变化年末负载变化技术约束技术约束通常主要是指：兼容性（指系统/应用的兼容性）关联性（如系统是摩格逻辑组的一部分）大部分环境下，这些约束包括了：网络连接（子网段级别）应用之间的互连性相关的存储使用技术所用的硬件和外设软件支持度和认证这些约束条件根据虚拟化在内核上下实现的不同而有所不同共享与分离OS镜像模式商业和流程的约束规模较小或集中的情况下容易被忽略的约束在实验室的测试环境可以不考虑，但生产环境必须要考虑在虚拟化中常见的商业和流程约束包括：维护窗口和冻结改变地理位置和其他物理限制运维环境，安全区域，应用分层部署考虑商业组织，部门以及客户法规政策的考虑与限制忽视这些约束条件将可能导致不可预知的结果具体情况具体分析，根据目标制定计划议程程应用用实实施施范范围围考考虑虑服务务器器采采购购考考虑虑虚拟拟机机部部署署考考虑虑管理理维维护护考考虑虑虚拟拟化化中中使使用用的的硬硬件件应应满满足足兼兼容容性性列列表表要要求求ESX服务务器器硬硬件件配配置置考考虑虑要要点点–CPUsESX调度度CPU周期期满满足足虚虚拟拟机机和和ServiceConsole的处处理理请请求求可用用的的CPU目标标数数量量越越多多，，ESX管理理这这个个调调度度机机制制的的效效果果越越好好（单单台台服服务务器器配配置置8个以以上上的的CPU核会会有有最最好好的的效效果果）超线线程程技技术术并并不不能能提提供供等等同同于于多多核核处处理理器器的的好好处处；；建建议议关关闭闭CPU的超超线线程程功功能能（（如如果果有有的的话话））使用用具具有有EM64T能力力的的IntelVT或AMDV技术术的的CPU可以以同同时时支支持持运运行行32位和和64位的的虚虚拟拟机机采用用同同一一厂厂商商、、同同一一产产品品家家族族和和同同一一代代处处理理器器的的服服务务器器组组成成的的集集群群，，可可以以获获得得最最好好的的VMotion兼容容能能力力ES的EnhancedVMotion兼容容性性扩扩大大了了原原有有VMotion的兼兼容容能能力力-《AlleviatingConstraintswithResourcePoolsLiveMigrationwithEnhancedVMotion》》参见见《BestPracticesforSuccessfulVIDesign》》ESX服务务器器硬硬件件配配置置考考虑虑要要点点-内存存内存存资资源源往往往往比比CPU资源源更更会会成成为为潜潜在在的的瓶瓶颈颈在某某些些时时候候，，虚虚机机环环境境的的内内存存使使用用量量可可能能会会超超过过物物理理内内存存值值：：Hostswapfile(尽量量少少用用以以获获得得最最佳佳性性能能)TransparentPageSharing（多多个个虚虚机机共共享享相相同同内内存存页页面面））注意意服服务务器器特特定定的的内内存存配配置置要要求求DIMMsizes,bankpairing,parity,upgradeconsiderations(mixandmatchorforkliftreplacement)尽可可能能将将服服务务器器配配置置到到最最大大内内存存，，采采用用最最大大容容量量的的内内存存条条（（特特别别是是当当没没有有配配满满全全部部内内存存条条时时））参见见《BestPracticesforSuccessfulVIDesign》》虚拟拟架架构构的的基基本本网网络络连连接接部部件件组组成成(Managementvirtualmachine)(Vmotion,iSCSI,NFS)(VMconnectivity)PortGroupPortGroupPortGroupESX服务务器器硬硬件件配配置置考考虑虑要要点点-网络络参见见《BestPracticesforSuccessfulVIDesign》》最少少配配置置一一个个虚虚拟拟交交换换机机，，测测试试环环境境可可用用2个虚拟交交换机，，生产环环境建议议最少配配置3个虚拟交交换机虚拟交换换机可同同时支持持3种类型的的端口组组(ServiceConsole,VMkernel,VM)建议将ServiceConsole、VMkernel和虚机端端口组各各自使用用自己的的虚拟交交换机可用VLAN技术分割割不同的的端口组组对于使用用VMotion和DRS功能的服服务器集集群，网网络配置置应该相相匹配（虚拟交交换机的的数量与与网络卷卷标名应应保持一一致）ESX服务器ServiceConsole使用固定定IP，配置正正确的speed和duplex。ESX服务器硬硬件配置置考虑要要点-网络-虚拟交换换机和端端口组参见《BestPracticesforSuccessfulVIDesign》ESX服务器，，虚拟交交换机，，物理网网卡出于冗余余的考虑虑，每个个虚拟交交换机建建议至少少分配两两个物理理网卡每个ESX服务器的的物理网网卡/口数量取取决于准准备配置置的虚拟拟交换机机的数量量如果3种类型的的端口组组（SC,VMkernel,VM）都在不不同的虚虚拟交换换机上，，生产环环境建议议至少6个物理网网卡/口如果给包包含虚拟拟机端口口组的虚虚拟交换换机分配配更多的的物理网网卡/口，可以以获得负负载均衡衡的好处处ESX服务器硬硬件配置置考虑要要点-网络基本本组件参见《BestPracticesforSuccessfulVIDesign》物理网卡卡/口与物理理交换机机同一个虚虚拟交换换机上的的不同物物理网卡卡/口应连接接到不同同的物理理交换机机上将一个集集群中所所有服务务器的VMotion功能端口口组所使使用的物物理网卡卡/口都连到到同一套套物理交交换机上上（同样遵遵循上述述第一条条规则））ESX服务器硬硬件配置置考虑要要点-与物理网网络的连连接参见《BestPracticesforSuccessfulVIDesign》Example1:BladeServerwith2NICPortsvSwitchvmnic0SCvmkernelActiveStandbyvmnic1CandidateDesign:TeambothNICportsCreateonevirtualswitchCreatethreeportgroups:UseActive/StandbypolicyforeachportgroupPortgroup1:ServiceConsole(SC)Portgroup2:VMotionPortgroup3:VMtrafficUseVLANtrunkingTrunkVLANs10,20,30oneachuplinkPortgroup1

VLAN10Portgroup3

VLAN30Portgroup2

VLAN20VLANTrunks(VLANs10,20,30)Example2:Serverwith4NICPortsvmnic0SCvmkernelActiveStandbyvmnic1CandidateDesign:CreatetwovirtualswitchesTeamtwoNICstoeachvSwitchvSwitch0(useactive/standbyforeachportgroup):Portgroup1:ServiceConsole(SC)Portgroup2:VMotionvSwitch1(useOriginatingVirtualPortID)Portgroup3:VMtraffic#1Portgroup4:VMtraffic#2UseVLANtrunkingvmnic1andvmnic3:TrunkVLANs10,20vmnic0andvmnic2:TrunkVLANs30,40Portgroup4

VLAN40VLANs10,20vSwitch0Portgroup1

VLAN10Portgroup2

VLAN20vSwitch1vmnic2vmnic3Portgroup3

VLAN30VLANs30,40Example3:Serverwith4NICPorts(SlightVariation)vmnic0SCvmkernelActiveStandbyvmnic1CandidateDesign:CreateonevirtualswitchCreatetwoNICteamsvSwitch0(useactive/standbyforportgroups1&2):Portgroup1:ServiceConsole(SC)Portgroup2:VmotionUseOriginatingVirtualPortIDforPortgroups3&4Portgroup3:VMtraffic#1Portgroup4:VMtraffic#2UseVLANtrunkingvmnic1andvmnic3:TrunkVLANs10,20vmnic0andvmnic2:TrunkVLANs30,40VLANs10,20vSwitch0Portgroup1

VLAN10Portgroup2

VLAN20vmnic2vmnic3Portgroup3

VLAN30VLANs30,40Portgroup4

VLAN40ServerswithMoreNICPortsMorethan4NICPorts——DesignConsiderationsWithTrunks(VLANtagging):UsepreviousapproachandscaleuptomeetadditionalbandwidthandredundancyrequirementsAddNICstoNICteamsupportingVMtrafficVLANTaggingalwaysrecommended,butoptionsifNICsavailable:DedicatedNICforVMotionAtleastoneNICDedicatedNICsforIPStorage(NFSand/oriSCSI)UsuallytwoteamedNICs(considerIP-hashðerchannelifmultipledestinations

andMulti-ChassisEtherchannelemployedonphysicalswitches)DedicatedNIC(s)forServiceConsoleAtleasttwoforavailabilityNote:easytoconsumemanyphysicalNICsandswitchportsifnotusingVLANtaggingESX服务器硬件件配置考虑虑要点-存储应尽可能采采用外置共共享磁盘阵阵列存放虚虚拟机文件件ESX服务器内置置硬盘应有有充分的冗冗余，建议议采用RAID1ESX服务器自身身对硬盘要要求，安装装时的Partition划分：不建议用安安装时的自自动硬盘划划分方法，，因为/、/var、/home会放再同一一个目录下下，当/(root)满了时，ESX服务器会发发生严重问问题。建议议：/boot 50到100MB(PrimaryPartition)/ 8.0到18GB(PrimaryPartition)(swap) 2倍的ServiceConsole内存,建议固定使使用1.6G/var4GB或更大建议足够的的ESX服务器程序序空间大小小为18GB本地端的ISO以及其他文文本文件的的存放空间间要考虑存储对于虚虚拟机的呈呈现方式7VM层数据存储存储阵列SCSI控制器虚拟磁盘呈呈现为SCSI控制器SCSI控制器显示示为BUS或LSILogic磁盘控制器器一个VM可具有1到4个虚拟LSILogic或BusLogicSCSI适配器每个SCSI适配器包含含1到15个虚拟SCSI存储设备虚拟磁盘驻驻留在可格格式化为VMFS、NFS或裸磁盘的的数据存储储中文件系统类类型由底层层物理磁盘盘驱动器器确确定VMFSNFSFCiSCSINAS卷、数据存存储和LUN卷存储阵列数据存储8LUN1020GBLUN是一个逻辑辑空间可由存储阵阵列的整个个空间创建建，也可由由其中的部部分空空间创建LUN映射到ESX后即成为卷卷当卷被格式式化为某种种文件系统统之后即成成为数据存存储不能在同一一个LUN中混用不同同类型的文文件系统每个LUN对应一个VMFS卷虚拟机内容容位于数据据存储中数据存储ESX数据存储类类型：VMware文件系统（VMFS）使用VMFS的RDM网络文件系系统（NFS）卷VM内容ESX主机数据存储采采用某种文文件系统格格式可以像操作作文件一样样操作数据据存储每个系统具具有256个VMFS数据存储每个系统具具有8个NFS数据存储ISO映像、VM模板和软盘盘映像9虚拟机内容容文件名说明<VM名称>.vmxVM配置<VM名称>.vmdk虚拟磁盘<VM名称>-flat.vmdk预分配的虚拟磁盘文件（包含数据）<VM名称>.vswp交换文件nvram非易失性RAM文件<VM名称>.vmemVM内存<VM名称>.vmssVM挂起文件<VM名称>.vmsd快照数据<VM名称>-Snapshot.vmsn快照状态文件VMware-0.log、vmware-1.log等日志文件10文件夹/子目录数据存储类类型数据存储VMFS数据存储VMFS数据存储NFSIP网络VM内容VM内容FC交换机光纤通道SAN磁盘阵列iSCSISAN磁盘阵列NAS磁盘阵列VM1ESX主机1VM2VM1ESX主机2VM2VM内容VM3VM312本地SCSIVMDKIP交换机ESX服务器建议议配置-新购为了尽可能能的发挥虚虚拟化的作作用，最大大限度的利利用单台服服务器的资资源，建议议用于虚拟拟化宿主服服务器的配配置应达到到或超过如如下标准：：服务器CPU路数双路四路八路CPU（建议主频2GHz以上）双路四核四路双核或四核四路双核或四核+内存16GB+32GB+64GB+千兆网口无外接存储4+/6+4+/6+4+/6+使用FC存储4+/6+4+/6+4+/6+使用IP存储6+/8+6+/8+6+/8+FCHBA口（建议4Gb或8Gb产品）222内置硬盘（使用外置磁盘阵列时）222电源双冗余双冗余双冗余从性价比和和可用性考考虑，不建建议在单路路服务器上上部署虚拟拟化虚拟化宿主主服务器建建议配置-现有对于目前业业内用的比比较多的四四路服务器器，建议议如下：四路单核服服务器：运运算能力较较弱，虚机机数量应控控制在10个以内，内内存配置建建议在12GB-16GB；四路双核服服务器：运运算能力中中等，虚机机数量可做做到10-15个左右，内内存配置建建议在16GB-24GB；四路四核服服务器：运运算能力强强劲，虚机机数量可做做到15-30个左右，内内存配置建建议在24GB-32GB。VC服务器最佳佳配置建议议处理器：2.0GHz或更高的Intel或AMDx86处理器，VC支持多处理理，可支持持至多2个CPU。内存：最低低需求为2GB，假使数据据库和VC安装于同一一台，建议议增加至4GB。磁盘空间：：最小为560MB，建议2GB。网卡：建议议用Gigabit。最低硬件配配置单个2GHzCPU，2GB内存，千兆兆网口可支持20个同时连接接，管理50台物理机，，1000个虚拟机左左右建议配置双CPU，4GB内存，千兆兆网口可支持50个同时连接接，管理200台物理机，，2000个虚拟机左左右议程应用实施范范围考虑服务器采购购考虑虚拟机部署署考虑管理维护考考虑虚机个数的的规划单台服务器器所能支持持虚机数量量的决定因因素：服务器的硬硬件配置CPU性能多核高主频频技术使得得CPU成为性能瓶瓶颈的可能能性越来越越低内存大小做为硬指标标的内存，，配置越高高，所能支支持的虚机机数量越多多网络端口千兆网环境境已很普遍遍，网络带带宽大多有有保证，更更多从管理理角度来考考虑HBA卡磁盘访问性能能对虚机数量量有一定影响响，建议采用用4Gb或8GbHBA卡以减少链路路影响本地磁盘内置磁盘的可可用性及IO吞吐能力均较较弱，不建议议在其上存放放虚拟机，推推荐使用外置置高性能磁盘盘阵列应用负载大小小由于物理服务务器资源自身身的最大限制制，应用负载载越大，所能能同时运行的的虚机数量越越少建议将不同应应用访问特性性的应用混合合部署在同一一物理服务器器上灵活运用DRS和VMotion技术可将物理理机与虚机的的比率关系调调到最优考虑到HA及DRS所要求的资源源冗余，所有有运行虚机在在正常负载下下，总体资源源使用率不超超过三分之二二会比较合适适经验值：双路路四核10个虚机左右，，四路四核15-30个虚机（仅为为参考）虚机资源的分分配CPU、内存CPU分配原则：尽量使用最少少的vCPUs，如果是单线线程应用，不不支持多线程程处理，请不不要使用virtualSMP虚拟CPU数量不要等于于或超过物理理CPU核数，如双路路双核服务器器配置的虚机机最多使用两两个虚拟CPU当配置虚拟机机的时候须了了解ESX服务器本身也也有一些overhead。需注意不要要超过所有虚虚拟机使用率率和所有vCPU汇总数目。观察”idleloopspin”功能参数，某某些操作系统统当它们闲置置时，并不会会真正的释放放virtualCPU。确认配置了单单一处理器的的虚拟机为””UPHAL/kernel”，多处理器的的虚拟机必须须设定为”SMPHAL/kernel”。内存分配原则则：内存总量为在在资源评估后后，计算虚拟拟机评估结果果所需实际物物理内存的总总和，其他由由于应用程序序而产生的更更多内存需要要可以用ESX的磁盘内存来来解决关键应用可考考虑固定内存存的方法以保保证性能的稳稳定性DRSBestPractices:HardwareConfigurationEnsurehostsareCPUcompatibleIntelvsAMDSimilarCPUfamily/SSE3statusEnhancedVMotionCompatibility(EVC)“VMwareVMotionandCPUCompatibility”whitepaperCPUincompatibility=>limitedDRSVMmigrationoptionsLargerHostCPUandmemorysizepreferredforVMplacement(ifallequal)Differencesincacheormemoryarchitecture=>inconsistencyinperformanceDRSBestPractices:ClusterConfigurationHighernumberofhosts=>moreDRSbalancingoptionsRecommendupto32hosts/clusterMayvarywithVCserverconfigurationandVM/hostratioNetworkconfigurationonallhostsVMotionnetwork:Securitypolicies,VMotionnicenabled,GigEnetwork,etcVirtualMachinenetworkpresentonallhostsVMdatastoresharedacrossallhostsVMfloppy/CDconnectedtohostdeviceDRSBestPractices:VMResourceSettingsReservations,Limits,andSharesSharestakeeffectduringresourcecontentionLowlimitscanleadtowastedresourcesHighVMreservationsmaylimitDRSbalancingOverheadmemoryUseresourcepools(RP)forbettermanageabilityVirtualCPU’sandMemorysizeHighmemorysizeandvirtualCPU’s=>fewermigrationopportunitiesConfigureVMsbasedonneedDRSBestPractices:AlgorithmSettingsAggressivenessthresholdModeratethreshold(default)workswellformostcasesAggressivethresholdsrecommendedifHomogenousclustersandVMdemandrelativelyconstantandFewaffinity/anti-affinityrulesUseaffinity/anti-affinityrulesonlywhenneedAffinityrules:closelyinteractingVMsAnti-affinityrules:I/Ointensiveworkloads,availabilityAutomaticDRSmoderecommended(cluster-wide)Manual/Partiallyautomaticmodeforlocation-criticalVMs(perVM)PerVMsettingoverridescluster-widesettingHABestPractices-Setup&NetworkingProperDNS&NetworksettingsareneededforinitialconfigurationAfterconfigurationDNSresolutionsarecachedto/etc/FT_HOSTS(minimizingthedependencyonDNSserveravailabilityduringanactualfailover)DNSoneachhostispreferred(manualeditingof/etc/hostsiserrorprone)RedundancytoESXServiceConsolenetworkingisessential(severaloptions)ChoosetheoptionthatminimizessinglepointsoffailureGateways/isolationaddressesshouldrespondviaICMP(ping)EnablePortFast(orequivalent)onnetworkswitchestoavoidspanningtreerelatedisolationsNetworkmaintenanceactivitiesshouldtakeintoaccountdependenciesontheESXServiceConsolenetwork(s)VMwareHAcanbetemporarilydisabledthroughtheCluster->EditSettingsdialogValidVMnetworklabelnamesrequiredforproperfailoverVirtualmachinesusethemtore-establishnetworkconnectivityuponrestartHANetworkConfigurationAsingleserviceconsolenetworkwithunderlyingredundancyisusuallysufficient:Useateamof2NICsconnectedtodifferentphysicalswitchestoavoidasinglepointoffailureConfigurevNicsinvSwitchforActive/Standbyconfiguration(rollingfailover=““yes”,defaultloadbalancing=routebasedonoriginatingportID)Considerextendingtimeoutvalues&addingmultipleisolationaddresses(*seeappendix)Timeoutsof30-60secondswillslightlyextendrecoverytimes,butwillalsoallowforintermittentnetworkoutagesNetworkredundancybetweentheESXserviceconsolesisessentialforreliabledetectionofhostfailures&isolationconditionsHANetworkConfiguration(Continued)HAwilldetectanduseasecondaryserviceconsolenetworkAddingasecondaryserviceconsoleportgrouptoanexistingVMotionvSwitchavoidshavingtodedicateanadditionalsubnet&NICforthispurposeAlsoneedtospecifyanadditionalisolationaddressfortheclustertoaccountfortheaddedredundancy(*seeappendix)Continueusingtheprimaryserviceconsolenetwork&IPaddressformanagementpurposesBecarefulwithnetworkmaintenancethataffectstheprimaryserviceconsolenetworkandthesecondary/VMotionnetworkBeyondNICteaming,asecondaryserviceconsolenetworkcanbeconfiguredtoprovideredundantheartbeating&isolationdetectionHABestPractices–ResourceManagementLargergroupsofhomogenousserverswillallowhigherlevelsofutilizationacrossanHA/DRSenabledcluster(onaverage)Morenodespercluster(currentmaximumis16)cantoleratemultiplehostfailureswhilestillguaranteeingfailovercapacitiesAdmissioncontrolheuristicsareconservativelyweighted(sothatlargeserverswithmanyVMscanfailovertosmallservers)Todefinethesizingestimatesusedforadmissioncontrol,setreasonablereservationsastheminimumresourcesneededAdmissioncontrolwillexceedfailovercapacitieswhenreservationsarenotset;otherwiseHAwilluselargestreservationspecifiedasthe““slot”size.Ataminimum,setreservationsforafewvirtualmachinesconsidered““average”AdmissioncontrolmaybetooconservativewhenhostandVMsizesvarywidelyPerformyourowncapacityplanningbychoosing““Allowvirtualmachinestobepoweredoneveniftheyviolateavailabilityconstraints”.HAwillstilltrytorestartasmanyvirtualmachinesasitcan.议程应用实实施范范围考考虑服务器器采购购考虑虑虚拟机机部署署考虑虑管理维维护考考虑ImpactofVirtualCenterDowntimeComponentImpactExperiencedVirtualMachinesUnaffected,managementrequiresdirectconnectionstoESXServersESXServersUnaffected,managementrequiresdirectconnectionstoESXServersPerformance&MonitoringStatisticsHistoricalrecordswillhavegapsduringoutages,stillavailableviaESXServersVMotionUnavailableVMwareDRSUnavailableVMwareHAAgentsunaffected&providefailoverfunctionality,admissioncontrolunavailable参见《BulletproofVirtualCenter-AGuidetoProtectingVirtualCenter》》VirtualCenterComponentsVirtualCenterServerWebAccessLicenseServerADDomainControllerDNSServerDatabaseServer参见《BulletproofVirtualCenter-AGuidetoProtectingVirtualCenter》》VirtualCenter––RecommendedCollocationCollocationofVirtualCentercomponentsisdesirableformostenvironmentsFocusofthissessionisonprovidingprotectionforthesecomponentsIndustrystandardsolutionsassumedforothercomponentsOneServer,PhysicalorVirtualVirtualCenterServerWebAccessLicenseServerADDomainControllerDNSServerDatabaseServer参见《BulletproofVirtualCenter-AGuidetoProtectingVirtualCenter》》VirtualCenterComponents(AdditionalDetails)VirtualCenterService:almoststatelessInformationaboutinventorystoredinthedatabaseSomestatefilesstoredlocallyonVirtualCenterserverWebAccessNostateinformationLicenseServerLicensefilestoredlocally14dayGraceperiodifunavailable参见《BulletproofVirtualCenter-AGuidetoProtectingVirtualCenter》》VirtualCenter––LocalConfigurationFilesOneServer,PhysicalorVirtualVirtualCenterServerWebAccessLicenseServerDatabaseServerSSLCertificateLicenseFileConfig.FileUpgradeFiles参见见《BulletproofVirtualCenter-AGuidetoProtectingVirtualCenter》》Step1forHighAvailability:ProtecttheDatabaseDatabaseoutagewillterminateVirtualCenterserviceAsofVirtualCenter2.0.1Patch2,WindowsServiceManagerwillautomaticallyattempttorestartitevery5minutes,indefinitelyVirtualCenterDatabaseshouldbeindependentlyinstalledandmanagedForlocalavailabilityusethepreferredmechanismforthetypeofdatabasebeingused(VMwareHA,MSCS,Databasespecificmechanisms)Fordisasterrecovery,databaseshouldbereplicatedtoaremotesiteaspartofanoverallDRplan参见见《BulletproofVirtualCenter-AGuidetoProtectingVirtualCenter》》VCVCBang!FailoverStep2forHighAvailability:ProtectVirtualCenterVMwareHAandMicrosoftClusterServices(MSCS)arethetwomostpopularoptionsOther3rdpartysolutionspossible**Supporteddirectlyby3rdpartyOptiona):VMwareHAVirtualinstancesonlySubjecttosharedstorage/networkconstraintsOnlyrequiressingleOS&applicationinstance;noexplicitreplicationOptionb):MSCSVirtualCenter2.0.2patch2orbeyondPhysicalorvirtualinstancesRequires2identicalOS&applicationinstallations;explicitreplicationoffilesInvolvesadditionalconfigurationefforts&ongoingmaintenance参见见《BulletproofVirtualCenter-AGuidetoProtectingVirtualCenter》》VirtualCenter:Physicalvs.VirtualPhysicalVirtualBackupsdoneusingtraditionaltoolsBackupspossiblethroughtraditionaltools,VCB,snapshots,cloning,etc.DedicatedserverrequiredDedicatedservernotrequired,resourcescanbesharedwithothervirtualmachinesPerformancelimitedonlybyserverhardwarePerformancefromsharedresources;tuningmaybeneededVirtualCenterwithVMwareHA:Out-of-BandTwoapproachesTwoVirtualCenterinstancesmanageeachother(pictured)BothruninHAclusterEachmanagestheother’’sHAclusterSeparateVirtualCenterinstanceisusedtomanage2-nodeHAcluster(notpictured)vpxdvpxdVirtualCenterServermanagestheVMwareHAclusterprovidingitsprotectionWhentheESXhostswithVirtualCenterVMfails,VMisrestartedautomaticallybyHAFailoverfunctionalityprovidedbyHAisindependentfromVirtualCenter(post-configuration)vpxdVirtualCenterwithVMwareHA:In-BandVirtualCenterwithMSCS––PhysicalBestpractice:useMajorityNodeSetquorumwithwitnessshareMaybeusedasgeographicallydispersedclusterfordisasterrecoverysolutionVCDBmaybeusedinanotherclustergrouponthesameclusterRequiresathirdnodeEthernetNetworkvcdbvpxdVirtualCenterwithMSCS––VirtualRequiresuseofquorumdiskclustering:QuorumdiskonthesharedstorageSystemdisksforbothclusteredvirtualmachinesonlocalstorageIncompatiblewithVMotionorVMwareHASANLANvpxdRiseofthePhoenix-DisasterRecoveryVirtualCenterServerDatabaseServerVIServicesVIInventoryDatabaseServerStandardDRSolutionStandbyVirtualCenterServerPrimaryReplicationofstatefilesVirtualCenterDisasterRecoveryOverviewDisasterrecoverysolutionconsistsofthreepieces:VIInventorydataUsethestandardDRsolutionofthedatabasevendorVIServicesColdStandby–Re-installVirtualCenterandrestorelocalconfigurationfilesWarmStandby–Pre-installVirtualCenterandsynchronizelocalconfigurationfiles,butkeep2ndinstancedisconnectedAllotherinfrastructureservices:AD,DNS,etc.Useexistingproduct-specificsolutionsColdStandbyRecoveryProcedureAbletoassignprimary’sIPtostandby?MaintainseparateuptodatecopyoflocalconfigurationfilesInstallfresh

VirtualCenterinstanceInstall

configfiles;connecttostandbyDBDisaster!ESXServerhosts

reconnectautomaticallyRunscripttoreconnectallESXServerhostsDoneyesnoWarmStandbyRecoveryProcedureAbletoassignprimary’’sIPtostandby?KeeplocalconfigurationfilessynchronizedbetweenprimaryandstandbyDisaster!ESXServerhostsreconnectautomaticallyRunscripttoreconnectallESXServerhostsDoneyesnoFasterend-to-endrecovery(RTO)AlsoallowsforscriptingandautomationReplicationofconfigurationfilesthroughhost-basedreplicationorbackuptoolsMonitoringIndividualVirtualCenterComponentsEntitySubentityComponentMetricTooltouseVirtualCenterServerVirtualCenterVirtualCenterService-vpxdvpxd.exefoundWMIvpxdisrunningasserviceWMIVirtualCenterCertificatesfilesareexistsWMIsizeWMImodificationdateWMILicenseServerLicenseServerServiceexefileexistsWMIserviceisupandrunningWMILicenseFilesfilesareexistsWMIsizeWMImodificationdateWMIWebServiceWebServiceexefileexistsWMIserviceisupandrunningWMIWebPagehttp://localhostisreachablePerlorvbsscript–HTTPGETcriticalfiles(?)arefoundWMIHostSystem(whereVCisrunningon)SystemCPUload<90%WMISystemdisk<80%FULLWMINetworkOKWMIDatabaseserverODBCConnectionConnectionworksWMIDatabaseintegritySome"select"statementoncriticaltablessqlFileContentsLocationFlexLicensefilesLicensekeysforallserver-basedlicensedfeaturesC:\ProgramFiles\VMware\VMwareLicenseServer\LicensesV