Chris McCain - Mastering VMware® Infrastructure3

It is also the use account used for the creation of the ODBC connection to the SQL Server 2005 computer. </p> <cite> <div class="title">Database Permissions Error </div> <p>At this stage in the installation you might receive the following error:</p> <p>The DB user entered does not have the required permissions needed to install and configure VMware VirtualCenter Server with the selected DB. Please see the installation documentation for detailed DB permission requirements.</p> <p>This is most commonly due to not providing the SQL user account with ownership of the VirtualCenter database or not providing db_owner database role membership for the MSDB database. It might be a bit of a struggle to convince database administrators to allow the db_owner membership for MSDB, but remember that the permission assignment can be removed once the installation is complete.</p> <p>If you have the luxury of making the SQL user account a sysadmin the installation will also run fine, however, if this is done it should be immediately undone after the installation. If you are using an existing SQL server managed by other database administrators chances are that they are not going to allow even temporary sysadmin membership.</p> </cite> <p>10. Click the OK button if your receive the following warning message: </p> <p>11. Please make sure SQL Server Agent service is running on the database server.</p> <p>12. If the SQL Server 2005 database has been left with the default configuration it will be set to Full Recovery model and a warning message will appear, click the OK button. The warning will suggest a VMware knowledge base article that will direct you to change the recovery model to Simple. If you are unsure of the ramifications of doing this please revisit an earlier section of this chapter where we discussed the Full versus Simple recovery model. Or ask your friendly neighborhood database administrator.</p> <p>13. On the VMware VirtualCenter Server Deployment Options-Step 2 page select the appropriate licensing strategy. The default selection will allow a 60 day evaluation. It is also possible to select the use of an existing licensing server or to configure the local server as a licensing server by using the Browse button to find a valid server-based licensing license file. If you choose to use and existing license server or configure the local server as a licensing server select the VirtualCenter edition from the drop down list. It is important to select the version that matches the license you have purchased else you will have to reconfigure VirtualCenter after installation. You can revisit the earlier section of this chapter that discussed the differences in licensing.</p> <p>14. If the installation is being installed to use the 60 day trial you will receive an information box regarding the trial period. Click the OK button to continue.</p> <p>15. On the VMware VirtualCenter Server Deployment Options-Step 3 page click the OK button to accept the default VirtualCenter port configuration. The ports can be edited if conflicts might occur with existing applications using similar ports. You should avoid altering the default port settings.</p> <p>16. On the VirtualCenter Server Authorization page provide the administrative credentials necessary for VirtualCenter to install the VirtualCenter extensions. Click the Next button to continue.</p> <p>17. On the VMware Update Manager Deployment Options-Step1 page, select the appropriate back-end database option for use by the VMware Update Manager. Provide the appropriate ODBC connection name and corresponding username and password. Once again a warning regarding the database recovery model might be presented. Click the OK button to proceed past the warning, then click the Next button to continue.</p> <p>18. On the VMware Update Manager Deployment Options-Step 2 page configure the appropriate name and port setting for the VMware Update Manager to use. You should avoid altering the default port settings. Click the Next button to continue.</p> <p>19. On the VMware Converter Enterprise Deployment Options page configure the appropriate name and port setting for use by the VMware Converter built into VirtualCenter. You should avoid altering the default port settings. Click the Next button to continue.</p> <p>20. On the Destination Folder selection page configure the installation directory for VirtualCenter and its components and the directory for storing updates downloaded by VMware Update Manager. Click the Next button to continue.</p> <p>21. Click the Install button to initiate the installation.</p> <p>22. After the installation is complete use the VMware Virtual Infrastructure Client to connection to the VirtualCenter Server installation.</p> <div class="title"> <p>Creating and Managing a VirtualCenter Inventory</p> </div> <p>Upon first connecting to VirtualCenter you will notice a getting started tab that facilitates the construction of a new datacenter. The starting point for the VirtualCenter inventory is called the root, while the building block of the VirtualCenter inventory is called a datacenter object. Along with the link for creating new data is a set of links to help you quickly find more information about getting the VirtualCenter up and running. The links in the Explore Further menu include:</p> <p>♦ Learn more about inventory views</p> <p>♦ Learn more about virtualization</p> <p>♦ Learn more about datacenter</p> <p>From the Hosts & Clusters node in the inventory tree, there are several tabs across (see Figure 5.27) for reviewing data about all objects beneath the Hosts & Clusters view root. Within each tab you can right click the column headers and select additional data to be reviewed or existing data to be removed. In addition to the Getting Started tab, the tabs available from the Hosts & Clusters root include:</p> <p>♦ Datacenters-viewing all datacenter objects as well as the number of hosts and virtual machines within</p> <p>♦ Virtual Machines-provides a list of virtual machines within the root as well as performance data, state, and host.</p> <p>♦ Hosts-provides a list of each host within the root as well as performance data and state of each host.</p> <p>♦ Tasks & Events-provides a listing of the most recent tasks and events that have taken place</p> <p>♦ Alarms-displays a list of alarms that have been defined to fire for each host or VM within the root</p> <p>♦ Permissions-provides information and configuration capability for delegating authority at the root level</p> <p>♦ Map-provides a tool for reviewing the virtualization architecture and the relationships between the various components.</p> <img src=#i_173.png" > <p> <strong>Figure 5.27</strong>Hosts & Clusters is the root of the VirtualCenter management utility.</p> <empty-line > <p>VirtualCenter is a dynamic application in that when a different object in the inventory is selected, the available tabs become customized for the selected object. For example, when an ESX Server host is selected in the inventory the available tabs change to reflect the administrative tasks and data for the host, shown in Figure 5.28. The tabs available when a host is selected include:</p> <p>♦ Summary</p> <p>♦ Virtual Machines</p> <p>♦ Resource Allocation</p> <p>♦ Performance</p> <p>♦ Configuration</p> <p>♦ Tasks & Events</p> <p>♦ Alarms</p> <p>♦ Permissions</p> <p>♦ Topology Maps</p> <img src=#i_174.Читать дальше