The first edition of this study guide was first published as a series of posts on my blog “Adventures in a Virtual World”, here.
These posts were written in preparation for my VCAP5-DCA exam (version VDCA510).
With the release of the VDCA550 exam in spring 2014, I felt I had to write a version for this exam as well. This guide is based on the VDCA550 Blueprint, version 3.2, as found here.
For more information about the differences between the VDCA510 and the VDCA550, read my post on this item.
This guide will meet the following goals:
- Based on the official Blueprint, follow the objectives as close as possible.
- Refer to the official VMware documentation as much as possible. For that reason, every Objective starts with one or more references to the VMware documentation.
- In case the official documentation is not available or not complete, provide an alternative.
- Write down the essence of every objective (the Summary part).
- If necessary, provide additional explanation, instructions, examples and references to other posts. All this without providing too much information.
In the official vSphere 5.0 documentation, all user actions are performed using the traditional vSphere Client. However in the vSphere 5.5 documentation almost all user actions are performed using the vSphere Web Client. In this revision, most pictures have been replaced; in some cases you will see the vSphere Client.
I hope all this will help you in your preparation for your exam. I welcome your comments, feedback and questions.
Download VCAP5-DCA exam VDCA550 – Section 1.
With vSphere 5.5 came many, many changes. Without a doubt, the biggest change is the prominent role of the vSphere Web Client, now being the preferred client to manage your vSphere Clusters.
Being very familiar with the traditional vSphere Client, it takes a reasonable amount of time to get used to the vSphere Web Client (vWC). In my case, I always tried to perform the action with the vWC, with the traditional Client for Fall-back or while in a hurry.
While refreshing my knowledge about Storage Profiles, I noticed, in vSphere 5.5 “Storage Profiles” have been renamed to “Storage Policies”.
Although, not quite. Figure 1, shows part of the home screen of the same vCenter 5.5 server.
Figure 1– [Left] vSphere Web Client – [Right] traditional vSphere Client
But, soon I discovered that not only the name of this feature has changed.
Read the rest of this entry »
With vSphere 5.0, VMware also introduced a new version of its vSphere Virtual Machine File System, known as VMFS-5. For a complete list of the new features, see the “What’s New in VMware vSphere 5.0 – Storage” whitepaper. Since vSphere 5.5, the maximum supported VMDK size on a VMFS-5 datastore has been increased from 2 TB to 62 TB. More information on this in KB 2058287 “Support for virtual machine disks larger than 2 TB in VMware ESXi 5.5”.
Although vSphere 5.x fully supports predecessor VMFS-3, it’s also possible to upgrade an existing VMFS-3 to VMFS-5. See also this whitepaper “VMware vSphere VMFS-5 Upgrade Considerations”
But beware; an upgraded VMFS-5 does not support all of the new features. Most noticeable are:
- An upgrade VMFS-5 continues to use the previous file-block size, which may be larger than the unified 1MB file-block size. This can lead to stranded/unused disk space when there are lots of small files on the datastore. It is also stated that this can affect the performance of subsequent Storage vMotions.
- An upgraded VMFS-5 datastore doesn’t have new features like; the new Sub-Block Size, Increased maximum number of files per datastore, no GPT.
- Also, VMFS-5 upgraded from VMFS-3 continues to have its partition starting on sector 128. Newly created VMFS-5 partitions will have their partition starting at sector 2048.
So, by deploying newly created VMFS-5 and upgraded VMFS-5 datastores, chances are that inconsistencies across your datastores are introduced.
So instead of upgrading existing datastores, another approach is rebuilding datastores (fresh formatted VMFS-5) and relocating your VM’s. Of course this takes some planning and you will need a spare LUN.
One question remains, how to recognize a new or an upgraded VMFS-5 datastore? OK, you can have a look in the vSphere Client or Web Client. If the Block Size is not 1 MB, it is an upgraded one. But now the block Size is 1 MB, can you be sure it is a newly created one?
Read the rest of this entry »
vCenter Orchestrator was an objective in the VDCA410 exam that qualified for the VCAP4-DCA certification, disappeared in the VDCA510 exam and returned in the VDCA550 exam
Skills and abilities
- Configure and manage vCenter Orchestrator
- Add Orchestrator to vCenter
- Create basic vCenter management workflows
- Troubleshoot existing workflows
- Import/export packages
Configure and manage vCenter Orchestrator
First of all, what is vCenter Orchestrator (vCO from now on)? According to the documentation, vCO is a development- and process-automation platform that provides a library of extensible workflows to allow you to create and run automated, configurable processes to manage the VMware vSphere infrastructure as well as other VMware and third-party technologies. The Key word in this definition is the word “process-automation”.
The architecture of vCO
Figure 1 – vCO Architecture (Source: VMware)
Read the rest of this entry »
This week, VMware released the new VDCA550 exam. This exam also qualifies for the VMware Certified Advanced Professional 5 – Data Center Administration (VCAP5-DCA) Certification.
So, now two exams qualify for this certification, the other being the VDCA510 exam that has been around since July 2012. The difference between those, the oldest exam is based on vSphere 5.0, the latest is based on vSphere 5.5.
With a new exam comes a new Exam Blueprint. Both blueprints can be found here.
Although the Exam Blueprint for the VDCA510 exam is currently on version 2.9, there are no changes in the Objectives since version 1.1.
So what has changed in the Exam Blueprint for the VDCA550 exam?
- Section 1.2, The number of live lab activities (VDCA550; 23 and VDCA510; 26).
- Section 1.6, The Time limit has changed (VDCA550; 180 minutes and VDCA510; 210). Both an additional 30 minutes for non-native English speakers.
- Section 1.12, the environment available during the exam is described in greater detail in the VDCA550 Blueprint. Also, the vSphere 5.5 environment consist of five ESXi 5.5 hosts, two vCenter 5.5 Servers, vCOPS 5.6 Foundation, vCenter Orchestrator 5.5 and vSphere Replication 5.5 appliances plus an Active Directory domain controller and shared storage.
- Section 1.13 presents an overview of the documentation available during the exam; links to the actual documentation are included in the Blueprint. You won’t find this overview in the VDCA510 Blueprint.
- Under the Objectives, all “Knowledge sections” have been disappeared in the VDCA550 Blueprint. Although some parts moved to the “Skills and Abilities” section.
- The VDCA550 Blueprint does not have a separate Troubleshooting section. Some troubleshooting objectives have been moved to other objectives.
- The VDCA510 Blueprint has a total of 9 sections; the VDCA550 Blueprint has 7 sections.
Read the rest of this entry »
On April 1, the vExperts 2014 are announced. Corey Romero, John Troyer, and the VMware Social Media & Community Team have named 754 vExperts. For the second time in a row, I have been selected for my (modest) contribution to the amazing VMware community. I feel proud, honoured and humbled at the same time.
Congratulations to all the other vExperts! Let’s continue and make it an awesome 2014.
The announcement and the complete list of vExperts can be found here.
I would like to thank all of you for making this possible.
In a previous post, I presented an overview of the ESXCLI command. This command is part of the vSphere CLI. For an introduction read the post I just mentioned.
The ESXCLI command has a lot of Namespaces and command options. To get some more insight, I created a Mind map. But that was in 2012 and vSphere 5.0 was the actual version. Since then, vSphere 5.1 and 5.5 were released and with that the ESXCLI has undergo a lot of enhancements.
So time for an update. This new version of the ESXCLI Mind map has the following enhancements:
- The previous version only contained namespaces. In this version, the command options have been added. Namespaces are normal font, command options are in Italic.
- All vSphere 5.1 additions are coloured in blue.
- All vSphere 5.5 additions are coloured in red.
Figure 1 – ESXCLI Namespaces
The Complete picture, so that makes clear why Mind mapping tools are so useful. :-)
Figure 2 – Complete picture
The Mind map can be downloaded from here. WordPress still does not allow me to upload .mm files. So after downloading the file, change the extension from .doc to .mm.
FreeMind, the free mind mapping tool I use, can be found here.