Vg archive how to#
Vg archive upgrade#
Vg archive free#

usr/lib/applmgmt/support/scripts/autogrow.sh

Run the autogrow.sh script to resize all filesystems to the virtual disk size.

Remove LVM labels from sdh # pvremove /dev/sdh.

Remove sdh from the Volume Group # vgreduce seat_vg /dev/sdh.

PV UUID V7lkDg-Fxyr-qX4x-d3oi-KhNO-XZyT-EHgibI

Vg archive free#

(Check that Allocated PE = 0 and nothing except FREE is listed in physical segments) # pvdisplay -m /dev/sdh

Verify that there are no physical segments.

When the migration is finished, sdh should be empty.

Move all physical extends from sdh to sdn # pvmove /dev/sdh /dev/sdn.

Now you should have to devices in the seat_vg - sdh (old large disk) and sdn (new small disk).

Add the sdn device to the Volumegroup (Identified in step 4: seat_vg) # vgextend seat_vg /dev/sdn.

Initialize the device to be used by LVM.

sd 2:0:14:0: Attached scsi generic sg17 type 0

Run dmesg to identify the latest device.

If you want to figure out the host adapter that is in use for virtual disks, run ' lsscsi'. dev/mapper/seat_vg-seat 296G 67M 283G 1% /storage/seat /sys/class/scsi_host/host2/scanДЄdditional note: You have to rescan host adapter ID 2 (host2). dev/mapper/dblog_vg-dblog 15G 86M 14G 1% /storage/dblog dev/mapper/core_vg-core 25G 44M 24G 1% /storage/core Note the filesystem and mount point you want to shrink.ДЇrom the Filesystem name, you can also identify the Volume Group ( seat_vg) and Logical Volume ( seat) # df -hДЇilesystem Size Used Avail Use% Mounted on In this example, /storage/seat has a size of 296GB but only 67 MB in use.

Select the filesystem you want to shrink.

Connect to the vCSA using SSH and login as root.

I recommend using a clone because when the process fails, you can simply delete the clone and start the working original. You just have to shrink the filesystem, reduce the logical volume size, and migrate the logical volume to a smaller virtual disk. When you are familiar with Linux and LVM, nothing special is going to happen here. Creating and working with a clone is a good practice here. I'm not a fan of snapshots when you are changing the Virtual Machine itself (adding and removing virtual disks). Currently, there is no supported way to shrink a vCenter Server.ДЇirst of all, you should make sure that you have a working backup. Warning: The procedure described here is not supported by VMware. While this shouldn't be a problem for the vCenter itself, it might result in problems when you need VMware GSS.

Vg archive upgrade#

I recommend using this method only before an upgrade because it will change the order of VMDKs attached to the vCenter.

Vg archive how to#

In this article, I'm describing how to shrink the Virtual machine to prevent it from growing during the upgrade. The system currently has 416 GB allocated, which means that I can't upgrade to 'Tiny'. Here is an example of a 'Tiny' vCSA 6.7 that I want to upgrade.

It doesn't matter how much is actually in use. When upgrading vCenter 6.7 to vCenter 7.0, the upgrader calculates the source machine size based on the old Virtual Machines Disks and allocated memory. In some cases, you might end up with a vCenter that has over 1TB of storage allocated, but less than 100GB in use. The reason for the growth is, whenever you upgrade the vCenter you have to select a bigger size. After upgrading a vCenter Server Appliance (vCSA) multiple times, it might result in having very large virtual disks.