【正文】 r 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 – Reinstall VirtualCenter and restore local configuration files Warm Standby – Preinstall VirtualCenter and synchronize local configuration files, but keep 2nd instance disconnected All other infrastructure services: AD, DNS, etc. Use existing productspecific solutions Cold Standby Recovery Procedure Able to assign primary’s IP to standby? Maintain separate up to date copy of local configuration files Install fresh VirtualCenter instance Install config files。 connect to standby DB Disaster! ESX Server hosts reconnect automatically Run script to reconnect all ESX Server hosts Done yes no Warm Standby Recovery Procedure Able to assign primary’s IP to standby? Keep local configuration files synchronized between primary and standby Disaster! ESX Server hosts reconnect automatically Run script to reconnect all ESX Server hosts Done yes no Faster endtoend recovery (RTO) Also allows for scripting and automation Replication of configuration files through hostbased replication or backup tools Monitoring Individual VirtualCenter Components Entity Sub entity Component Metric Tool to use VirtualCenter Server Virtual Center Virtual Center Service vpxd found WMI vpxd is running as service WMI Virtual Center Certificates files are exists WMI size WMI modification date WMI License Server License Server Service exe file exists WMI service is up and running WMI License Files files are exists WMI size WMI modification date WMI Web Service Web Service exe file exists WMI service is up and running WMI Web Page is reachable Perl or vbs script – HTTP GET critical files (?) are found WMI Host System (where VC is running on) System CPU load 90% WMI System disk 80% FULL WMI Network OK WMI Database server ODBC Connection Connection works WMI Database integrity Some select statement on critical tables sql File Contents Location Flex License files License keys for all serverbased licensed features C:\Program Files\VMware\VMware License Server\Licenses VirtualCenter Configuration file Governs the behavior of VirtualCenter Server and its interaction with ESX Server hosts as well as client programs, such as the VI Client. C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\ SSL certificate The certificate used to authenticate all munication with ESX Server hosts. %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\SSL Upgrade files In special circumstances, it might be necessary to make custom changes to the agent which gets pushed to ESX Server hosts as they are added to the environment C:\Program Files\VMware\VMware VirtualCenter \upgrade VirtualCenter – Important Files (Details) VirtualCenter Communication Ports Communication Channel Default Port Number and Protocol Configurable? VirtualCenter to ESX Server host 902。 TCP and UDP Not easily (requires numerous manual config file changes) VirtualCenter to VI Client 902。 TCP and 443。 TCP for initiation Yes, via VI Client Web browser to VirtualCenter 80 443。 TCP Yes, via VI Client 3rd party SDK client to VirtualCenter 80 443。 TCP Yes, via VI Client Web browser to virtual machine console 903。 TCP No VI Client to virtual machine console 903。 TCP No VI Client to ESX Server host 902。 TCP and 443。 TCP for initiation No Web browser to ESX Server host 443。 TCP No 3rd party SDK client to ESX Server host 443。 TCP No Historical Past Day Past Week Past Month Past Year Rollup every 30 minutes 5 min Hostd Hostd Real Time statistics collection Database VPXD rolls up real time performance statistics to historical five minutes statistics and sends to database VirtualCenter Rollup every 2 hours Rollup every 24 hours 30 min 2 hr 24 hr Purge after one year Overview of Performance Statistics Database Sizing for Optimal Performance Memory databases are most efficient when given enough memory to cache their working data set Disk I/O sufficient disk device bandwidth for log devices to prevent transactions from bottlenecking on disk I/O CPU SQL Server is designed to use parallel processing whenever possible SQL Server’s TEMPDB used extensively in VMware VirtualCenter not as much in VMware VirtualCenter VMware VirtualCenter Performance Tips Configure performance statistics levels for collection levels (see next slide) configure past day and past week statistics at level 3 past month and past year statistics at level 1. fewer performance statistics for historical data Benefits significant reduction in the size of VMware VirtualCenter database. significant reduction in processing of rollups 謝 謝 演講完畢，謝謝觀看！