Skip to main content

List of VMDKs in vCenter Server 7.0 Appliance

 

In vCenter Server Appliance 7.0, there are 16 VMDKs now. In  vCenter Server Appliance 6.7 version it was 13 disks. Additional 3 new disks in this release are as follow:

 

·         vTSDB Service Repository for stats

·         vTSDB Service Repository for logs

·         Lifecycle for binaries (install, update and upgrade). 

There are multiple ways in which we can access information about disks. Below are some of the examples. 

·         We can check usage from vimtop about disks, however vimtop does not show all disks.



·         Complete list of disks can be seen in Appliance VM edit settings as well.

·         You can check these disks from VAMI as shown in below screenshot.


·         We can use df -h command to retrieve disk information as shown below.




·         Another way to access this information is lsblk command on vCenter shell as shown below.





Below is the complete list of VMDKs along with their usages and mount points.

Note: 

Below sizes are application only for vCenter Server Appliance 7.0 with tiny specification and default size and hence will differ in your environment as per inventory specification.

·         VMDK1

·         Size:

·         12 GB

·         Mount Points:

·         / (10GB)

·         /boot (132MB)

·         SWAP (1GB)

·         Usage:

·         Directory where the kernel images and boot loader configurations are stored.

·         VMDK2

·         Size:

·         1.8 GB

·         Mount Point:

·         /tmp

·         Usage:

·         Directory used to store temporary files generated or used by services from vCenter Server

·         VMDK3

·         Size:

·         25 GB

·         Mount Point:

·         SWAP

·         Usage:

·         Directory used when the system is out of memory to swap to disk

·         VMDK4

·         Size:

·         25 GB

·         Mount Point:

·         /storage/core

·         Usage:

·         Directory where core dumps from VPXD process from the vCenter Server are stored

·         VMDK5

·         Size:

·         10 GB

·         Mount Point:

·         /storage/log

·         Usage:

·         Directory where vCenter Server and Platform Services Controller store all logs for the environment

·         VMDK6

·         Size:

·         10 GB

·         Mount Point:

·         /storage/db

·         Usage: 

·         VMware Postgres database storage location

·         VMDK7

·         Size: 

·         5 GB

·         Mount Point:

·         /storage/dblog

·         Usage:

·         VMware Postgres database logging location

·         VMDK8

·         Size:

·         10 GB

·         Mount Point:

·         /storage/seat

·         Usage:

·         Stats, Events, Alarms and Tasks (SEAT) directory for VMware Postgres

·         VMDK9

·         Size:

·         1 GB

·         Mount Point:

·         /storage/netdump

·         Usage:

·         VMware Netdump collector repository that stores ESXi dumps

·         VMDK10

·         Size:

·         10 GB

·         Mount Point:

·         /storage/autodeploy

·         Usage: 

·         VMware Auto Deploy repository that stores the thinpackages used for stateless booting of ESXi hosts

·         VMDK11

·         Size:

·         10 GB

·         Mount Point:

·         /storage/imagebuilder

·         Usage:

·         VMware Image Builder repository that stores the vSphere image profiles, software depots and VIB packages, such as driver VIBs and update VIBs.

·         VMDK12

·         Size:

·         100 GB

·         Mount Point:

·         /storage/updatemgr

·         Usage:

·         VMware Update Manager repository where patches and updates are stored for Virtual Machine and ESXi hosts

·         VMDK13

·         Size:

·         50 GB

·         Mount Point:

·         /storage/archive

·         Usage:

·         VMware Postgres database’s Write-Ahead Logging (WAL) location

·         VMDK14

·         Size:

·         10 GB

·         Mount Point:

·         /storage/vtsdb

·         Usage:

·         VMware vTSDB Service Repository that stores the stats

·         VMDK15

·         Size:

·         5 GB

·         Mount Point:

·         /storage/vtsdblog

·         Usage:

·         VMware vTSDB Service Repository that stores the logs of the service


·         VMDK16

·         Size:

·         100 GB

·         Mount Point:

·         /storage/lifecycle

·         Usage: 

·         Workload Control Plane service stage directory or software depot, this stores the binaries for install and update/upgrade.





Labels:

Comments

Post a Comment

Popular posts from this blog

vCenter Server Options on VxRail Appliance

In this post we will discuss the pros and cons of vCenter Server deployment on VxRail. During VxRail initialization we can choose two options for vCenter Server deployment, both options are “Deploy new vCenter Server Appliance (VCSA)” and “Join existing vCenter Server”. We should know its limitation before we choose the each option. You can find the details as below. If we choose the bundle vCenter Server deployment The vCenter Service Server Appliance (VCSA), vCenter Server Platform Services Controller (PSC) and vRealize Log Insight VM are already pre-loaded on each VxRail node. When VxRail initialization it can deploy these VMs automatically based on our business requirement. Pros The vCenter Server (VCSA) deployment is done automatically. When installing software package upgrade for the VxRail Manager, both VCSA and PSC includes the processing of package upgrade. VMware Log Insight is deployed automatically The vCenter license is bundled on VxRail Appliance. C...
1 comment
Read more

Console Mouse Not Working in Windows 2012 VMs

I recently ran into some problems while deploying a Windows Server 2012 R2 VM in my vSphere 6.5 U2 lab. I’ve come to expect that the console mouse response is going to be terrible until VMware Tools is installed, but for some odd reason I had no mouse control whatsoever. Thinking it may be a quirk of the Web Console, I tried both the Remote Console and the HTML5 client to no avail. The VM appeared to be healthy and would register keyboard input, but the motion of the mouse cursor was erratic or the cursor would not move at all. Thinking that I just needed to battle on and get Tools installed, I attempted to use the keyboard for this purpose – what a chore. You think it would have been easy, but the installer kept losing focus and falling behind other open windows. Many of the windows keyboard shortcuts I’d normally use were not functioning because they register on my laptop – not in the console. I couldn’t RDP to the VM either because the NIC needed to be configured with a vali...
Post a Comment
Read more

1. Learning NSX-T: Introduction

VMware NSX is one of the most sensational product that VMware produced 5 years back post Niciria acquisition and over the years this product has just gone better and better. NSX revolutionized the SDDC by adding the SDN capabilities and they way how SDN was used before NSX.  One of the major limitation of NSX-V was that it can be used only with vSphere and not with other platforms and customers were continuously demanding for a version of NSX that can be integrated with non-vSphere platforms. To overcome this challenge, VMware came up with NSX-T which is version of NSX for non-vSphere based infrastructure. This version of NSX can be integrated with other hypervisiors such as KVM and application frameworks such as Redhat Openshift, Docker/Containers and Pivotal. In addition to these platforms, you can integrate your vSphere platform as well with NSX-T. As we know that in NSX-V, vCenter was centralized management plane but NSX-T has its own management interface. As of now NSX-...
Post a Comment
Read more