VMware虛擬化最佳實踐及規(guī)劃

虛假化最正的確踐及規(guī)劃議程應用實行范圍考慮服務器采買考慮虛假機部署考慮管理保護考慮議程應用實行范圍考慮服務器采買考慮虛假機部署考慮管理保護考慮應用實行范圍整體原則不適合采用虛假化的應用擁有特別硬件接見要求的應用高性能圖形顯卡不合用虛假化特別的串/并行加密設備不合用虛假化USB設備連結需求可能不合用，可采用外置USB設備取代，需經過測試即使在高配置的服務器上仍舊擁有很高負載的應用可能不合用，需分析目前服務器配置狀況能夠采用虛假化的應用除上述不適合采用虛假化的應用以外的所有應用可依據應用遷移的復雜程度決定虛假化先后次序較易實現P2V的應用可先做遷移，如可用Converter工具直接遷移的應用較難或不可以做P2V遷移的應用可考慮采用從頭安裝方式后遷依據管理的需要決定能否做虛假化虛假化轉變過程對現有業(yè)務的影響程度轉變?yōu)樘摷倩髮ΜF有管理的影響程度部門之間協調的難易程度虛假化宿主服務器的部署種類垂直擴展與水平擴展部署模式不同資源池的“量子化”模型物理主機HypervisorVMOSAppVMOSAppVMOSAppVMOSAppVMOSAppVMOSAppVMOSAppVMOSAppVMOSAppPhysicalHostHypervisorVMOSAppVMOSAppVMOSAppPhysicalHostHypervisorVMOSAppVMOSAppVMOSApp物理主機HypervisorVMOSAppVMOSAppVMOSApp不同資源池的種類垂直擴展的主機模式供應更大的連續(xù)性資源空間更簡單滿足不同負載的符合性要求可供應更高的資源利用率水平擴展的集群主機模式更像是一組小池子的會合多組小容量資源池需要更多的監(jiān)控管理模塊化使用既有優(yōu)點也有弊端影響虛假化部署的參數系統(tǒng)功能的多樣化服務器的重要性獨立服務器不重要重要(獨立的,當地儲存等等)(群集的,多主機的等等)服務器農場(水平擴展服務器群集，公用服務器等等)(后端辦公,當地應用等等)負載拘束技術拘束商業(yè)拘束困難度增加負載拘束不同的資源組都需要分別考慮CPU利用率磁盤I/O網絡I/O內存利用率虛假化造成的額外負載平時也要做必定考慮，如磁盤和網絡的I/O會增加CPU的負擔iSCSI儲存接見也會增加CPU負擔運維的周期性負載變化也一定考慮進來月底負載變化年關負載變化技術拘束技術拘束平時主若是指：兼容性（指系統(tǒng)/應用的兼容性）關系性（如系統(tǒng)是摩格邏輯組的一部分）大多半環(huán)境下，這些拘束包含了：網絡連結（子網段級別）應用之間的互連性有關的儲存使用技術所用的硬件和外設軟件支持度和認證這些拘束條件依據虛假化在內核上下實現的不同而有所不同共享與分別OS鏡像模式商業(yè)和流程的拘束規(guī)模較小或集中的狀況下簡單被忽視的拘束在實驗室的測試環(huán)境能夠不考慮，但生產環(huán)境一定要考慮在虛假化中常有的商業(yè)和流程拘束包含：保護窗口和凍結改變地理地點和其余物理限制運維環(huán)境，安全地區(qū)，應用分層部署考慮商業(yè)組織，部門以及客戶法例政策的考慮與限制忽視這些拘束條件將可能以致不可預知的結果詳細狀況詳細分析，依據目標擬定計劃議程應用實行范圍考慮服務器采買考慮虛假機部署考慮管理保護考慮虛假化中使用的硬件應滿足兼容性列表要求所實用于實現VMwareVI3虛假架構解決方案的設備，包含：服務器系統(tǒng)、儲存系統(tǒng)、IO卡設備等，應滿足VMwareVI3產品兼容列表的要求，最新的兼容列表可從以下的連結找到：服務器系統(tǒng)兼容列表《HCL:SystemsCompatibilityGuideForESXServer3.5andESXServer3i》儲存系統(tǒng)兼容列表《HCL:Storage/SANCompatibilityGuideForESXServer3.5andESXServer3i》IO卡設備兼容列表，包含網卡、FCHBA卡和iSCSIHBA卡等《HCL:I/OCompatibilityGuideForESXServer3.5andESXServer3i》ESX服務器硬件配置考慮重點–CPUsESX調動CPU周期滿足虛假機和ServiceConsole的辦理懇求可用的CPU目標數目越多，ESX管理這個調動體制的成效越好（單臺服務器配置8個以上的CPU核會有最好的成效）超線程技術其實不可以供應等同于多查辦理器的利處；建議封閉CPU的超線程功能（假若有的話）使用擁有EM64T能力的IntelVT或AMDV技術的CPU能夠同時支持運行32位和64位的虛假機采用同一廠商、同一產品家族和同一代辦理器的服務器構成的集群，能夠獲取最好的VMotion兼容能力ES的EnhancedVMotion兼容性擴大了原有VMotion的兼容能力-《AlleviatingConstraintswithResourcePoolsLiveMigrationwithEnhancedVMotion》拜見《BestPracticesforSuccessfulVIDesign》ESX服務器硬件配置考慮重點-內存內存資源常常比CPU資源更會成為潛伏的瓶頸在某些時候，虛機環(huán)境的內存使用量可能會超出物理內存值：Hostswapfile(盡量少用以獲取最正確性能)TransparentPageSharing（多個虛機共享相同內存頁面）注意服務器特定的內存配置要求DIMMsizes,bankpairing,parity,upgradeconsiderations(mixandmatchorforkliftreplacement)盡可能將服務器配置到最大內存，采用最大容量的內存條（特別是當沒有配滿所有內存條時）拜見《BestPracticesforSuccessfulVIDesign》虛假架構的基本網絡連結零件構成(Managementvirtualmachine)(Vmotion,iSCSI,NFS)(VMconnectivity)PortGroupPortGroupPortGroupESX服務器硬件配置考慮重點-網絡拜見《BestPracticesforSuccessfulVIDesign》最少配置一個虛假交換機，測試環(huán)境可用2個虛假交換機，生產環(huán)境建議最少配置3個虛假交換機虛假交換機可同時支持3種種類的端口組(Service

Console,VMkernel,VM)建議將ServiceConsole、VMkernel和虛機端口組各自使用自己的虛假交換機可用VLAN技術切割不同的端口組對于使用VMotion和DRS功能的服務器集群，網絡配置應當相般配（虛假交換機的數目與網絡卷標名應保持一致）ESX服務器ServiceConsole使用固定IP，配置正確的speed和duplex。ESX服務器硬件配置考慮重點-網絡-虛假交換機和端口組拜見《BestPracticesforSuccessfulVIDesign》ESX服務器，虛假交換機，物理網卡出于冗余的考慮，每個虛假交換機建議最少分派兩個物理網卡每個ESX服務器的物理網卡/口數目取決于準備配置的虛假交換機的數目假如3種種類的端口組（SC,VMkernel,VM）都在不同的虛假交換機上，生產環(huán)境建議最少6個物理網卡/口假如給包含虛假機端口組的虛假交換機分派更多的物理網卡/口，能夠獲取負載均衡的利處ESX服務器硬件配置考慮重點-網絡基本組件拜見《BestPracticesforSuccessfulVIDesign》物理網卡/口與物理交換機同一個虛假交換機上的不同物理網卡/口應連結到不同的物理交換機上將一個集群中所有服務器的VMotion功能端口組所使用的物理網卡/口都連到同一套物理交換機上（相同依照上述第一條規(guī)則）ESX服務器硬件配置考慮重點-與物理網絡的連結拜見《BestPracticesforSuccessfulVIDesign》Example1:BladeServerwith2NICPortsvSwitchvmnic0SCvmkernelActiveStandbyvmnic1CandidateDesign:TeambothNICportsCreateonevirtualswitchCreatethreeportgroups:UseActive/Standbypolicy

foreachportgroupPortgroup1: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/standby

forportgroups1&2):Portgroup1:ServiceConsole(SC)Portgroup2:VmotionUseOriginatingVirtualPortID

forPortgroups3&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區(qū)分：不建議用安裝時的自動硬盤區(qū)分方法，因為/、/var、/home會放再同一個目錄下，當/(root)滿了時，ESX服務器會發(fā)生嚴重問題。建議：/boot50到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或裸磁盤的數據儲存中

文件系統(tǒng)種類由基層物理磁盤驅動

器確定VMFSNFSFCiSCSINAS卷、數據儲存和LUN卷儲存陣列數據儲存8LUN1020GBLUN是一個邏輯空間可由儲存陣列的整個空間創(chuàng)立，也可由其中的

部分空間創(chuàng)立

LUN映照到ESX后即成為卷

當卷被格式化為某種文件系統(tǒng)以后即成為數據儲存不可以在同一個LUN中混用不同種類的文件系統(tǒng)每個LUN對應一個VMFS卷

虛假機內容位于數據儲存中數據儲存ESX數據儲存種類：

VMware文件系統(tǒng)（VMFS）使用VMFS的RDM網絡文件系統(tǒng)（NFS）卷VM內容ESX主機數據儲存采用某種文件系統(tǒng)格式

能夠像操作文件相同操作數據儲存

每個系統(tǒng)擁有256個VMFS數據儲存

每個系統(tǒng)擁有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快照狀態(tài)文件VMware-0.log、vmware-1.log等日志文件10文件夾/子目錄數據儲存種類數據儲存VMFS數據儲存VMFS數據儲存NFSIP網絡VM內容VM內容FC交換機光纖通道SAN磁盤陣列iSCSISAN磁盤陣列NAS磁盤陣列VM1ESX主機1VM2VM1ESX主機2VM2VM內容VM3VM312當地SCSIVMDKIP交換機ESX服務器建議配置-新購為了盡可能的發(fā)揮虛假化的作用，最大限度的利用單臺服務器的資源，建議用于虛假化宿主服務器的配置應達到或超出以下標準：服務器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電源雙冗余雙冗余雙冗余從性價比和可用性考慮，不建議在單路服務器上部署虛假化虛假化宿主服務器建議配置-現有對于目前業(yè)內用的比許多的四路服務器，建議以下：四路單核服務器：運算能力較弱，虛機數目應控制在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個虛假機左右議程應用實行范圍考慮服務器采買考慮虛假機部署考慮管理保護考慮虛機個數的規(guī)劃單臺服務器所能支持虛機數目的決定因素：服務器的硬件配置CPU性能多核高主頻技術使得CPU成為性能瓶頸的可能性愈來愈低內存大小做為硬指標的內存，配置越高，所能支持的虛機數目越多網絡端口千兆網環(huán)境已很廣泛，網絡帶寬大多有保證，更多從管理角度來考慮HBA卡磁盤接見性能對虛機數目有必定影響，建議采用4Gb或8GbHBA卡以減少鏈路影響當地磁盤內置磁盤的可用性及IO吞吐能力均較弱，不建議在其上寄存虛假機，介紹使用外置高性能磁盤陣列應用負載大小因為物理服務器資源自己的最大限制，應用負載越大，所能同時運行的虛機數目越少建議將不同應用接見特征的應用混淆部署在同一物理服務器上靈巧運用DRS和VMotion技術可將物理機與虛機的比率關系調到最優(yōu)考慮到HA及DRS所要求的資源冗余，所有運行虛機在正常負載下，整體資源使用率不超出三分之二會比較適合經驗值：雙路四核10個虛機左右，四路四核15-30個虛機（僅為參照）虛機資源的分派CPU、內存CPU分派原則：盡量使用最少的vCPUs，假如是單線程應用，不支持多線程辦理，請不要使用virtualSMP虛假CPU數目不要等于或超出物理CPU核數，如雙路雙核服務器配置的虛機最多使用兩個虛假CPU當配置虛假機的時候須認識ESX服務器自己也有一些overhead。需注意不要超出所有虛假機使用率和所有vCPU匯總數目。觀察”idleloopspin”功能參數，某些操作系統(tǒng)當它們閑置時，其實不會真切的開釋virtualCPU。確認配置了單一辦理器的虛假機為”UPHAL/kernel”，多辦理器的虛假機一定設定為”SMPHAL/kernel”。內存分派原則：內存總量為在資源評估后，計算虛假機評估結果所需實質物理內存的總和，其余因為應用程序而產生的更多內存需要能夠用ESX的磁盤內存來解決重點應用可考慮固定內存的方法以保證性能的穩(wěn)固性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):MSCSPhysicalorvirtualinstancesRequires2identicalOS&applicationinstallations;explicitreplicationoffilesInvolvesadditionalconfigurationefforts&ongoingmaintenance拜見《BulletproofVirtualCenter-AGuidetoProtectingVirtualCenter》VirtualCenter:Physicalvs.VirtualPhysicalVirtualBackupsdoneusingtraditionaltoolsBackupspossiblethroughtraditionaltools,VCB,snapshots,cloning,etc.DedicatedserverrequiredDedicatedservernotrequired,resourcescanbesharedwithothervirtualmachinesPerformancelimitedonlybyserverhardwarePerformancefromsharedresources;tuningmaybeneededForadditionaldetailsrefertothefollowingdocumentation:VirtualCenterwithVMwareHA:Out-of-BandTwoapproachesTwoVirtualCenterinstancesmanageeachother(pictured)BothruninHAclusterEachmanagestheother’sHAclusterSeparateVirtualCenterinstanceisusedtomanage2-nodeHAcluster(notpictured)vpxdvpxdVirtualCenterServermanagestheVMwareHAclusterprovidingitsprotectionWhentheESXhostswithVirtualCenterVMfails,VMisrestartedautomaticallybyHAFailoverfunctionalityprovidedbyHAisindependentfromVirtualCenter(post-configuration)vpxdVirtualCenterwithVMwareHA:In-BandVirtualCenterwithMSCS–PhysicalBestpractice:useMajorityNodeSetquorumwithwitnessshareMaybeusedasgeographicallydispersedclusterfordisasterrecoverysolutionVCDBmaybeusedinanotherclustergrouponthesameclusterRequiresathirdnodeEthernetNetworkvcdbvpxdForadditionaldetailsrefertothefollowingdocumentation:VirtualCenterwithMSCS–VirtualRequiresuseofquorumdiskclustering:QuorumdiskonthesharedstorageSystemdisksforbothclusteredvirtualmachinesonlocalstorageIncompatiblewithVMotionorVMwareHASANLANvpxdForadditionaldetailsrefertothefollowingdocumentation:RiseofthePhoenix-DisasterRecoveryVirtualCenterServerDatabaseServerVIServicesVIInventoryDatabaseServerStandardDRSolutionStandbyVirtualCenterServerPrimaryReplicationof

statefilesVirtualCenterDisasterRecoveryOverviewDisasterrecoverysolutionconsistsofthreepieces:VIInventorydataUsethestandardDRsolutionofthedatabasevendorVIServicesColdStandby–Re-installVirtualCenterandrestorelocalconfigurationfilesWarmStandby–Pre-installVirtualCenterandsynchronizelocalconfigurationfiles,butkeep2ndinstancedisconnectedAllotherinfrastructureservices:AD,DNS,etc.Useexistingproduct-specificsolutionsColdStandbyRecoveryProcedureAbletoassign

primary’sIPto

standby?Maintainseparate

uptodatecopyof

localconfiguration

filesInstallfresh

VirtualCenter

instanceInstall

configfiles;

connectto

standbyDBDisaster!ESXServerhosts

reconnect

automaticallyRunscripttoreconnect

allESXServerhostsDoneyesnoForadditionaldetailsrefertothenewVIperltoolkit:WarmStandbyRecoveryProcedureAbletoassign

primary’sIPto

standby?Keeplocal

configurationfiles

synchronizedbetween

primaryandstandbyDisaster!ESXServerhosts

reconnect

automaticallyRunscripttoreconnect

allESXServerhostsDoneyesnoFasterend-to-endrecovery(RTO)AlsoallowsforscriptingandautomationReplicationofconfigurationfilesthroughhost-basedreplicationorbackuptoolsMonitoringIndividualVirtualCenterComponentsEntitySubentityComponentMetricTooltouseVirtualCenterServerVirtualCenterVirtualCenterService-vpxdvpxd.exefoundWMIvpxdisrunningasserviceWMIVirtualCenterCertificatesfilesareexistsWMIsizeWMImodificationdateWMILicenseServerLicenseServerServiceexefileexistsWMIserviceisupandrunningWMILicenseFilesfilesareexistsWMIsizeWMImodificationdateWMIWebServiceWebServiceexefileexistsWMIserviceisupandrunningWMIWebPagehttp://localhostisreachablePerlorvbsscript–HTTPGETcriticalfiles(?)arefoundWMIHostSystem(whereVCisrunningon)SystemCPUload<90%WMISystemdisk<80%FULLWMINetworkOKWMIDatabaseserverODBCConnectionConnectionworksWMIDatabaseintegritySome"select"statementoncriticaltablessqlFileContentsLocationFlexLicensefilesLicensekeysforallserver-basedlicensedfeaturesC:\ProgramFiles\VMware\VMwareLicenseServer\LicensesVirtualCenterConfigurationfileGovernsthebehaviorofVirtualCenterServeranditsinteractionwithESXServerhostsaswellasclientprograms,suchasthe