How to add additional space for backups on the SDDC Manager Utility virtual machine
search cancel

How to add additional space for backups on the SDDC Manager Utility virtual machine

book

Article ID: 316757

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

This article will provide instructions for adding additional space for backups to the SDDC Manager Utility virtual machine.

Symptoms:
By default, the /backup folder is shared with the rest of the / filesystem and is only 12GB in size. In larger VMware Cloud Foundation 2.2 environments, this might not be sufficient space for all of the required backups and the / filesystem might become full.

Resolution

  1. Log in to the vSphere Web Client as a use with administrative privileges.
  2. Right-click the SDDC Manager Utility virtual machine and select Edit Settings.
  3. Increase the sizes of Hard Disk 1 from 12 GB to 100 GB.
  4. Click the OK button.
  5. Right-click the SDDC Manager Utility virtual machine, select Power and then select Restart Guest OS.
  6. ssh to the SDDC Manager Utility virtual machine as the root user.
Note: The password for the root account on the SDDC Manager Utility virtual machine can be obtained by running the /home/vrack/bin/lookup-passwords command on the SDDC Manager Controller virtual machine.
  1. Issue the parted command. At the (parted) prompt, type print.
Note: The following message will be displayed;

Warning: Not all of the space available to /dev/sda appears to be used, you can
fix the GPT to use all of the space (an extra 184549376 blocks) or continue with
the current setting?
Fix/Ignore?

Type Fix

Note: The following should be displayed:

Model: VMware Virtual disk (scsi)
Disk /dev/sda: 107GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system     Name  Flags
 1      1049kB  135MB   134MB   ext3
 2      135MB   1209MB  1074MB  linux-swap(v1)
 3      1209MB  12.9GB  11.7GB  ext3
 4      12.9GB  12.9GB  3129kB                        bios_grub

Type quit to exit the parted utility.

  1. Type fdisk /dev/sda. At the command prompt, type F to see the unpartitioned space.
Note: Output similar to the following should be returned:

Unpartitioned space /dev/sda: 88 GiB, 94489263616 bytes, 184549343 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Type n to create a new partition. Press the Enter key at all prompts, accepting all default values.
Type w to save the partition.

  1. Issue the partprobe command to update the running kernel with the new partition information.
  2. Type fdisk -l /dev/sda to list the new partition table. 
Note: Output similar to the following should be returned.

Disk /dev/sda: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1A7A6FD0-CC96-4C94-88B0-6B3521E11166

Device        Start       End   Sectors  Size Type
/dev/sda1      2048    264191    262144  128M Linux filesystem
/dev/sda2    264192   2361343   2097152    1G Linux filesystem
/dev/sda3   2361344  25159679  22798336 10.9G Linux filesystem
/dev/sda4  25159680  25165790      6111    3M BIOS boot
/dev/sda5  25165824 209715166 184549343   88G Linux filesystem

Note: /dev/sda5 is the newly created partition.

  1. Type mkfs.ext3 /dev/sda5 to create a new filesystem on the /dev/sda5 partition.
Note: Output similar to the following should be returned:

mke2fs 1.42.13 (17-May-2015)
Creating filesystem with 23068667 4k blocks and 5767168 inodes
Filesystem UUID: 8880bfd7-6d2b-4f64-8952-7e3011fef199
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

  1. Issue the following commands to mount the new filesystem to /backup and relocate the original /backup contents to the new filesystem:
mv /backup /backup.orig
mkdir /backup
mount /dev/sda5 /backup
cp -rfp /backup.orig/* /backup/
rm -rf /backup.orig/*
  1. Open the /etc/fstab file in a text editor:
vi /etc/fstab
  1. Add the following to the end of the file:

/dev/sda5       /backup ext3    defaults,barrier,noatime,noacl,data=ordered     1       1

Save and close the file.

  1. Change the ownership of the /backup folder:
chown –R backupuser:backupgroup /backup
  1. Issue the reboot command to reboot the SDDC Manager Utility virtual machine.
  2. When the SDDC Manager Utility virtual machine is back up, ssh to it again as the root user.
  3. Issue the df -h command to verify that the /backup filesystem was mounted as expected.
Note: Output similar to the following should be returned:

Filesystem                             Size  Used Avail Use% Mounted on
devtmpfs                               3.9G     0  3.9G   0% /dev
tmpfs                                  3.9G     0  3.9G   0% /dev/shm
tmpfs                                  3.9G  648K  3.9G   1% /run
tmpfs                                  3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/sda3                               11G  3.0G  7.1G  30% /
tmpfs                                  3.9G     0  3.9G   0% /tmp
/dev/sda1                              120M   27M   87M  24% /boot
/dev/mapper/data_vg-lcm--bundle--repo  1.7T   69M  1.6T   1% /mnt/lcm-bundle-repo
tmpfs                                  798M     0  798M   0% /run/user/0
/dev/sda5                               87G  1.1G   82G   2% /backup

  1. Remove the original contents of the /backup folder:
rm -rf /backup.orig


Powered by Wolken Software