Database Reference
In-Depth Information
space needs to be calculated into your storage request.
Getting the Lab Up and Running
We have two ESXi 5.5 hosts we will be using for the test. Prior to building our virtual
machines, it is important to have the base foundation for the infrastructure configured.
We have vCenter Server running as a virtual machine. We have already downloaded
and configured the vCOPs, Hyperic, and Virtual Infrastructure Navigator virtual
appliances. We installed and configured these virtual appliances according to best
practices, which can be found in each product's Installation and Configuration
documentation available on VMware.com . Once our foundation was configured, we
installed the following virtual machines on our ESXi hosts (see Figure 11.1 ):
AD_2012, which is the Windows Server 2012 virtual machine configured with
AD DS, domain name s2012dir.domain
SQL_2012_a and SQL_2012_b, both running Windows Server 2012 Datacenter
Edition and SQL Server 2012 Enterprise and are members of the s2012dir.domain
LoadGen, which is the Windows 8.1 virtual machine and also a member of the
s2012dir.domain
Figure 11.1 Snapshot of the lab.
Using vCenter Infrastructure Navigator, we can display and understand the relationships
between these systems. We will revisit vCenter Infrastructure Navigator after we have
installed and configured SQL Server 2012 with AlwaysOn Availability Groups to
identify the changes. vCenter Infrastructure Navigator automatically generates the visual
shown in Figure 11.2 and automatically updates this as dependencies evolve. At the end
of our configuration, you will see an updated screenshot of Figure 11.2 that shows how
vCenter Infrastructure Navigator automatically updated the configuration and
connections based on our implementation of clustering, AlwaysOn Availability, and the
virtual machine driving the test workload.
 
 
 
Search WWH ::




Custom Search