From 637ed1a9a9360c357a884155e8cf90ccf0e20f1b Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Wed, 11 Dec 2024 17:45:31 +0200 Subject: [PATCH] changes to creating-vddk-iamge --- documentation/modules/creating-vddk-image.adoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/documentation/modules/creating-vddk-image.adoc b/documentation/modules/creating-vddk-image.adoc index ddde81292a6..11e48b74e72 100644 --- a/documentation/modules/creating-vddk-image.adoc +++ b/documentation/modules/creating-vddk-image.adoc @@ -6,17 +6,17 @@ [id="creating-vddk-image_{context}"] = Creating a VDDK image -{the} {project-first} can use the VMware Virtual Disk Development Kit (VDDK) SDK to accelerate transferring virtual disks from VMware vSphere. +You can use the VMware Virtual Disk Development Kit (VDDK) SDK to accelerate transferring virtual disks from VMware vSphere and reduce the risk of a migration plan migrating these disks from failing. + +To use this feature, you download the VMware Virtual Disk Development Kit (VDDK), build a VDDK image, and push the VDDK image to a secure registry that is accessible to all clusters. + +The VDDK package contains symbolic links, therefore, the procedure of creating a VDDK image must be performed on a file system that preserves symbolic links (symlinks). [NOTE] ==== -Creating a VDDK image, although optional, is highly recommended. +Creating a VDDK image is optional, but highly recommended. ==== -To make use of this feature, you download the VMware Virtual Disk Development Kit (VDDK), build a VDDK image, and push the VDDK image to your image registry. - -The VDDK package contains symbolic links, therefore, the procedure of creating a VDDK image must be performed on a file system that preserves symbolic links (symlinks). - [NOTE] ==== Storing the VDDK image in a public registry might violate the VMware license terms.