虚拟化最佳实践及规划 议程 应用实施范围考虑 服务器采购考虑 虚拟机部署考虑 管理维护考虑 议程 应用实施范围考虑 服务器采购考虑 虚拟机部署考虑 管理维护考虑 应用实施范围总体原则 不适合采用虚拟化的应用 具有特殊硬件访问要求的应用 高性能图形显卡 - 不适用虚拟化 特殊的串/并行加密设备 -不适用虚拟化 USB设备连接需求 - 可能不适用，vSphere 4.1可映射主机的USB设备到虚拟机，但需要测试 验证可用性，也可采用外置USB设备代替，同样需要经过测试确认 otherwise HA will use largest reservation specified as the “slot” size. At a minimum, set reservations for a few virtual machines considered “average” Admission control may be too conservative when host and VM sizes vary widely Perform your own capacity planning by choosing “Allow virtual machines to be powered on even if they violate availability constraints”. HA will still try to restart as many virtual machines as it can. 议程 应用实施范围考虑 服务器采购考虑 虚拟机部署考虑 管理维护考虑 Impact of VirtualCenter Downtime ComponentImpact Experienced Virtual Machines Unaffected, management requires direct connections to ESX Servers ESX Servers Unaffected, management requires direct connections to ESX Servers Performance no explicit replication Option b): MSCS VirtualCenter 2.0.2 patch 2 or beyond Physical or virtual instances Requires 2 identical OS explicit replication of files Involves additional configuration efforts tuning may be needed For additional details refer to the following documentation: VirtualCenter with VMware HA: Out-of-Band Two approaches Two VirtualCenter instances manage each other (pictured) Both run in HA cluster Each manages the others HA cluster Separate VirtualCenter instance is used to manage 2-node HA cluster (not pictured) vpxd vpxd VirtualCenter Server manages the VMware HA cluster providing its protection When the ESX hosts with VirtualCenter VM fails, VM is restarted automatically by HA Failover functionality provided by HA is independent from VirtualCenter (post- configuration) vpxd VirtualCenter with VMware HA: In-Band VirtualCenter with MSCS Physical Best practice: use Majority Node Set quorum with witness share May be used as geographically dispersed cluster for disaster recovery solution VCDB may be used in another cluster group on the same cluster Requires a third node Ethernet Network vcdb vpxd For additional details refer to the following documentation: VirtualCenter with MSCS Virtual Requires use of quorum disk clustering: Quorum disk on the shared storage System disks for both clustered virtual machines on local storage Incompatible with VMotion or VMware HA SAN LAN vpxd For additional details refer to the following documentation: Rise of the Phoenix - Disaster Recovery VirtualCenter Server Database Server VI Services VI Inventory Database Server Standard DR Solution Standby VirtualCenter Server Primary Replication of state files VirtualCenter Disaster Recovery Overview Disaster recovery solution consists of three pieces: VI Inventory data Use the standard DR solution of the database vendor VI Services Cold Standby Re-install VirtualCenter and restore local configuration files Warm Standby Pre-install VirtualCenter and synchronize local configuration files, but keep 2nd instance disconnected All other infrastructure services: AD, DNS, etc. Use existing product-specific solutions Cold Standby Recovery Procedure Able to assign primarys IP to standby? Maintain separate up to date copy of local configuration files Install fresh VirtualCenter instance Install config files; connect to standby DB Disaste r! ESX Server hosts reconnect automatically Run script to reconnect all ESX Server hosts Done yes no For additional details refer to the new VI perl toolkit: Warm Standby Recovery Procedure Able to assign primarys IP to standby? Keep local configuration files synchronized between primary and standby Disaste r! ESX Server hosts reconnect automatically Run script to reconnect all ESX Server hosts Done yes no Faster end-to-end recovery (RTO) Also allows for scripting and automation Replication of configuration files through host-based replication or backup tools Monitoring Individual VirtualCenter Components EntitySub entityComponentMetricTool to use VirtualCenter Server Virtual CenterVirtual Center Service - vpxdvpxd.exe foundWMI vpxd is running as serviceWMI Virtual Center Certificatesfiles are existsWMI size WMI modification dateWMI License ServerLicense Server Serviceexe file existsWMI service is up and runningWMI License Filesfiles are existsWMI size WMI modification dateWMI Web ServiceWeb Serviceexe file existsWMI service is up and runningWMI Web Page http:/localhost is reachable Perl or vbs script HTTP GET critical files (?) are foundWMI Host System (where VC is running on) System CPU load 90%WMI System disk 80% FULLWMI Network OKWMI Database serverODBC ConnectionConnection worksWMI Database integritySome “select“ statement on critical tablessql FileContentsLocation Flex License files License keys for all server-based licensed features C:Program FilesVMwareVMware License ServerLicenses VirtualCenter Configuration file Governs the behavior of VirtualCenter Server and its interaction w