Information Technology Reference
In-Depth Information
For small installations (up to 5 hosts and 50 VMs), VUM can use an instance of SQL Server
2008 R2 Express Edition (SQL Express). SQL Express is included on the VMware vCenter media,
and the VUM installation will automatically install and coni gure the SQL Express instance
appropriately. No additional work is required outside of the installation routine. However, as
you learned in Chapter 3, “Installing and Coni guring vCenter Server,” SQL Express does have
some limitations, so plan accordingly. If you do plan on using SQL Express, you can skip ahead
to the section “Installing VUM.”
If you decide against using SQL Express, you must now make another decision: Where do
you put the VUM database? Although it is possible for VUM to use the same database as vCen-
ter Server, it is strongly recommended that you use a separate database, even if you keep both
databases on the same database server. When you move beyond 100 hosts or 1,000 VMs, you
should be sure to use separate database servers for both the vCenter Server database and the
VUM database as well as separate servers for vCenter Server and the VUM server software.
Other factors, such as high availability or capacity, may also affect this decision. Aside from
knowing which database server you'll use, the decision to use a single computer versus multiple
computers won't affect the procedures described in this section.
In either case, there are specii c coni guration steps that you'll need to follow, just as you did
when installing vCenter Server. You'll need to create and coni gure the database, assign owner-
ship, and grant permissions to the MSDB database. Be sure to complete these steps before trying
to install VUM because this information is required during installation.
Perform the following steps to create and coni gure a Microsoft SQL Server 2005/2008/2012
database for use with VUM:
1.
Launch the SQL Server Management Studio application. When prompted to connect to a
server, connect to a supported database server. Select Database Engine as the server type.
2.
From the Object Explorer on the left side, expand the server node at the top level.
3.
Right-click the Databases node and select New Database.
4.
In the New Database window, specify a database name. Use a name that is easy to iden-
tify, such as VUM or vSphereUM.
5.
Set the owner of the new database.
Unless you are running the separate database on the same computer as VUM, you will
need to set the owner of the database to an SQL login; integrated Windows authentication
is not supported with a remote database.
Figure 4.1 shows a new database being created with an SQL login set as the owner.
6.
For ideal performance, set the location of the database and log i les so they are on differ-
ent physical disks or VMDKs than the operating system and the patch repository. Scroll
along to the right of the large pane to set the locations.
Figure 4.2 shows the database and log i les stored on a separate drive from the operating
system.
7.
After the settings are coni gured, click OK to create the new database.
As with the vCenter Server database, the login that VUM will use to connect to the database
server must have dbo permissions on the new database as well as on the MSDB database.
