Migrate vSphere (ESXi) Installation to a new Storage Device

From Thomas-Krenn-Wiki
Jump to navigation Jump to search

With the release of vSphere 7.0 Update 3, VMware announced that after the ESXi 7.x releases, the installation of the hypervisor on a USB stick or SD cards will no longer be supported.[1] Although no other storage medium is yet required for the current versions, it is important to plan accordingly for the upcoming ESXi releases. In this article, we explain the upcoming requirements and show different approaches to migrate the installation.

Requirements to the boot data medium

In KB article 85685[2] VMware describes the requirements for the data storage of future versions. It is recommended to store the OS data on a new disk. In many cases, it is a good idea to install a new M.2 SSD, since it can be installed without much effort. However, a new 2.5" SAS or SATA SSD, SATADOM or even a PCIe NVMe can also be used without hesitation.

To ensure many years of high-performance and stable operation, the selected memory type must meet the following minimum requirements:

  • 32GB memory space - 128GB is recommended.
  • Lifetime of 138 TBW
  • Sequential write speed of 100MB/s
  • Sequenzielle Schreibgeschwindigkeit von 100MB/s

Our Sales team will be happy to advise you which storage solutions are suitable for your Thomas-Krenn.AG server.

Migration by Backup & Restore

The easiest way to move the ESXi installation to a new disk is by backing up the host configuration and then restoring it.

Note: For ESXi versions 6.7 and earlier, the command is firmwareConfig.sh

Replace boot disk using Clonezilla

If there are signs that the boot disk is about to fail, cloning can be used to move the installation to a new disk of the same size. In this article, CloneZilla is used because it is based on a live OS and thus the cloning process can be performed directly on the host. Of course, programs such as Acronis True Image can be used if you connect the storage media to a suitable PC.

Cloning a disk can lead to data loss if done incorrectly. We therefore advise you to create a backup of the host configuration and data beforehand.

Note: Do not use this procedure when upgrading from a small storage medium, such as a USB stick, to a larger SSD. During cloning, the partition table of the old disk is copied 1:1. The VMFSL partition, where the ESX-OSData is stored, cannot be extended afterwards.

References

Author: Florian Sebald

Related articles

Increasing the size of a virtual disk in VMware
Monitoring MegaRAID Controllers in VMware
VMware Horizon details