Information Technology Reference
In-Depth Information
you have a few workloads that should not be automatically moved to other hosts using
vMotion. Can you use DRS? If so, how can you prevent these specii c workloads from be-
ing affected by DRS?
Solution Yes, you can use DRS. Enable DRS on the cluster, and set the DRS automation
level appropriately. For those VMs that should not be automatically migrated by DRS,
coni gure a VM Override set to Manual. This will allow DRS to make recommendations
on migrations for these workloads but it will not actually perform the migrations.
Coni gure and manage Storage DRS. Building on Storage vMotion just as vSphere DRS
builds on vMotion, Storage DRS automates the process of balancing storage capacity and
I/O utilization. Storage DRS uses datastore clusters and can operate in Manual or Fully
Automated mode. Numerous customizations exist—such as custom schedules, VM and
VMDK anti-afi nity rules, and threshold settings—to allow administrators to i ne-tune the
behavior of Storage DRS for their specii c environments.
Master It Name the two ways in which an administrator is notii ed that a Storage DRS
recommendation has been generated.
Solution On the Storage DRS tab of a datastore cluster, the recommendation(s) will be
listed with an option to apply the recommendations. In addition, on the Alarms tab of the
datastore cluster, an alarm will be triggered to indicate that a Storage DRS recommenda-
tion exists.
Master It What is a potential disadvantage of using drag-and-drop to add a datastore to
a datastore cluster?
Solution When you use drag-and-drop to add a datastore to a datastore cluster, the user
is not notii ed if the datastore isn't accessible to all the hosts that are currently connected
to the datastore cluster. This introduces the possibility that one or more ESXi hosts could
be “stranded” from a VM's virtual disks if Storage DRS migrates them onto a datastore
that is not accessible from that host.
Chapter 13: Monitoring VMware vSphere Performance
Use alarms for proactive monitoring. vCenter Server offers extensive alarms for alerting
vSphere administrators to excessive resource consumption or potentially negative events.
You can create alarms on virtually any type of object found within vCenter Server, including
datacenters, clusters, ESXi hosts, and VMs. Alarms can monitor for resource consumption
or for the occurrence of specii c events. Alarms can also trigger actions, such as running a
script, migrating a VM, or sending a notii cation email.
Master It What are the questions a vSphere administrator should ask before creating a
custom alarm?
Solution You should ask yourself several questions before you create a custom alarm:
Does an existing alarm meet my needs?
Will vC Ops alert me without needing a custom alarm?
What is the proper scope for this alarm? Do I need to create it at the datacenter
level so that it affects all objects of a particular type within the datacenter or at
some lower point?
 
Search WWH ::




Custom Search