Attention: This guide is only for 6.0 and 6.0 U1 version. Before use it on a production environment please test it to your lab.
First of all lets make a simple diagram on how it is the numbering of the VMDKs in order to know which specific VMDK we have to increase.
VMDK1 / and boot
VMDK2 Temp Mount
VMDK7 DB Log (dblog)
VMDK8 SEAT (Stats, Events & Tasks)
VMDK11 Inventory Service
The good thing about the different VMDKs is:
- We can increase a specific VMDK based on our needs. Like, when we have our DBLog partition full, so we can increase it without the need of increasing the root partition.
- We can have storage tiering policies in our VMDKs. It means that, for example if we need, we can have our DB partition to the SSD storage tiering in order to have faster DB transactions and operations.
So in order to increase the disk capacity the 1st Step is to extend the specific VMDK we want from the Edit Settings menu of the UI.
Then in the 2nd and last step, we can just connect via ssh to the appliance and run the simple command:
[firstname.lastname@example.org:~]# vpdx_servicecfg storage lvm autogrow
When disk grow you will see an output similar to this:
And we are ready, if we run the command ~# df -h , we will see that the partition we choosed increased, and we have more free space.
P.S If your bash shell is not enabled on your vCenter Server Appliance you can enable it with the below command, if you login via ssh to your VCSA and run:
~# shell.set –enabled true