2,187
edits
Difference between revisions of "Virtual Centre"
Jump to navigation
Jump to search
→Update Manager: Added "Best Practice"
(→Virtual Machine won't export: Updated with OVF Tool info) |
(→Update Manager: Added "Best Practice") |
||
| Line 153: | Line 153: | ||
# Restart the VMware Update Manager Service | # Restart the VMware Update Manager Service | ||
=== Best Practice === | |||
As advised by VMware, see http://www.vmware.com/files/pdf/techpaper/vsp_41_perf_UpdateManager_Best-Practices.pdf for further info | |||
* Separate the Update Manager database from the vCenter database when there are 300+ virtual machines or 30+ hosts. | |||
* Separate both the Update Manager server and the Update Manager database from the vCenter Server system and the vCenter Server database when there are 1000+ virtual machines or 100+ hosts. | |||
* Make sure the Update Manager server host has at least 2GB of RAM to cache patch files in memory. | |||
* Allocate separate physical disks for the Update Manager patch store and the Update Manager database. | |||
* Deploy the Update Manager server close to the ESX hosts if possible. This reduces network latency and packet drops. | |||
* On a high-latency network, powered-on virtual machine scans are preferred because they are not sensitive to network latency. | |||
* Host operations in a slow network will take a long time. Refer to the white paper for the maximum time estimation. Don’t interrupt ongoing operations. | |||
== SQL Database == | == SQL Database == | ||