VCAP-DCV Deploy Objective 2.2 – part 3

Home / Storage / VCAP-DCV Deploy Objective 2.2 – part 3

In this post we will continue to discuss the Manage Complex Storage Solutions objective

Here are the objective from the blueprint that we going to cover in this post:

  • Apply space utilization data to manage storage resources
  • Provision and manage storage resources according to Virtual Machine requirements
  • Configure datastore alarms, including Virtual SAN alarms
  • Expand (Scale up / Scale Out) Virtual SAN hosts and diskgroups

 

Lab Setup:

Using VMware workstation:

  • Microsoft Servers 2012R2 for Services (DNS , DHCP, etc…)
  • installed esx0/esx1/esx2
  • Installed VCSA
  • iSCSI Storage

 Documents used:

  • vSphere6 Storage Guide
  • VMware Virtual SAN administration Guide

Apply space utilization data to manage storage resources:

To get information about the space utilization  you can look at the datastore utilization by clicking on the datastore and then clicking on the summary tab to get the overall usage of the datatstore

dastore_util1

You can then drill down to see which VM’s are connected to the datastore and the space they using.

dastore_util2

Provision and manage storage resources according to Virtual Machine requirements:

When you provision storage for a VM you need to consider the followings:

  • Storage Controller, I covered this part in VCAP-DCV Deploy Objective 1.4 post
  • Type of disk (RDM, Virtual disk)
  • Virtual disk configuration (Thin/thick)

When choosing datastore you will need to consider all the topics that we discussed so far in “The Storage Objective” which i already covered.

One exam question that i think can come up with this objective is to convert a thin VM disk to a thick one , so lets try it

The process is simple , look for the datastore that the VM is using (for this task i use linux3 vm on iSCSI1 datastore

thintothick1

Browse the datatstore and look for the vmdk file right click and click on Inflate , also noticed the disk size

thintothick2

After the task is done look at the disk size.

thintothick3

Configure datastore alarms, including Virtual SAN alarms:

To set an Datastore alarm click on the Alarm Definition under the datastore and then click on (+) sign

alarm1

Create the condition and set the action

alarm2

As for vSAN you define an alarm the same way but vCenter Server does not have default alarms for certain vSAN host, cluster or disk state-changes. Check out VMware KB 2091347 for information

here is an one example from the KB article , using the “esx.problem.vob.vsan.pdl.offline” VOB

alarm3

The KB asks to configure the following VOBs:

  • esx.problem.vob.vsan.pdl.offline
  • esx.problem.vob.vsan.lsom.diskerror
  • esx.problem.vsan.lsom.congestionthreshol
  • esx.problem.vob.vsan.lsom.componentthreshold

Expand (Scale up / Scale Out) Virtual SAN hosts and diskgroups:

To expand vSAN you can hosts to the cluster or add more disks. Adding hosts to vSAN cluster is just like adding additional host to a cluster without vSAN

When you use vSAN in manual mode, you can add additional local devices to existing disk groups. The devices that you intend to add must be of the same type as the ones existing in the disk groups. Since i configure the vSAN to use manual discovery i will need to claim the disk first and than add the disk to the disk group

vvsan1

vvsan3

vvsan4

 

Thanks for reading

Mordi.

 

Leave a Reply

Your email address will not be published. Required fields are marked *