Difference between revisions of "Virtual Centre"
Jump to navigation
Jump to search
(→Troubleshooting: Added "Orphaned VM") |
(→Install: Added "Architecture Suggestions") |
||
| Line 4: | Line 4: | ||
For a production installation you should have a ready to use SQL database server (MS or Oracle), for small installations you can use MS SQL Express (which is installed as part of the vCentre install when no external database is specified). | For a production installation you should have a ready to use SQL database server (MS or Oracle), for small installations you can use MS SQL Express (which is installed as part of the vCentre install when no external database is specified). | ||
This is a basic install that will get you going, see [http://kb.vmware.com/kb/1022101 Installing ESX 4.1 and vCenter Server 4.1 best practices] for more info. | This is a basic install that will get you going, see [http://kb.vmware.com/kb/1022101 Installing ESX 4.1 and vCenter Server 4.1 best practices] for more detailed info, or the [[#Architecture Suggestions|Architecture Suggestions]] section below for some hints. | ||
'''SQL DSN requirements''' | '''SQL DSN requirements''' | ||
| Line 118: | Line 118: | ||
| 4.1 Update 1 || 345043 | | 4.1 Update 1 || 345043 | ||
|} | |} | ||
=== Architecture Suggestions === | |||
The following are some suggestions on how set-up your VI management infrastructure, take all of the below with a large amount of consideration for your specific requirements. For example, even if you've a small number of ESX's, if you're always performing lots of tasks you may want to consider beefing up your management infrastructure. | |||
* '''Install on Virtual machines''' (rather than physical) | |||
** VI management is resilient to hardware failures/maintenance through HA and vMotion | |||
** Besides, you can hardly expect service owners to be comfortable with virtualisation if you're not confident enough to locate your own systems on the platform! | |||
* '''Install both vCentre and SQL on the same VM''' | |||
** Installing on separate machines is of little benefit, and if they're always together the VC service becomes impervious to network and other problems (it readily fails if it has trouble access the SQL database). | |||
* '''Join the VM to the domain''' | |||
** Makes user management so much easier (and its more secure that way) | |||
* '''Install vCentre to run using a Local System account''' | |||
** If a domain service account, you can't start vCentre without the domain, which might be a big problem if you're DC's are virtual and your starting up following a power-down | |||
** If a local admin/service account, you can't browse/add domain users/groups to your vCentre permissions | |||
* '''Virtual hardware''' | |||
** 2 - 4 vCPU's (2 is fine for small installations) | |||
** 4 - 6 GB RAM (2 for OS, SQL, and vCentre respectively, 4GB total fine for small installations) | |||
== General Configuration == | == General Configuration == | ||