Skip to content

Commit

Permalink
Merge pull request #590 from anarnold97/MTV-1683-vMotion-should-be-di…
Browse files Browse the repository at this point in the history
…sabled

MTV-1683: vMotion should be disabled for VMs getting imported
  • Loading branch information
fabiand authored Nov 21, 2024
2 parents efa1f17 + 1b06238 commit 40fb086
Showing 1 changed file with 8 additions and 1 deletion.
9 changes: 8 additions & 1 deletion documentation/modules/running-migration-plan.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -36,4 +36,11 @@ Warm migration only:
. Click a migration's *Status*, whether it failed or succeeded or is still ongoing, to view the details of the migration.
+
The *Migration details by VM* screen opens, displaying the start and end times of the migration, the amount of data copied, and a progress pipeline for each VM being migrated.
. Expand an individual VM to view its steps and the elapsed time and state of each step.
. Expand an individual VM to view its steps and the elapsed time and state of each step.


[WARNING]
====
vMotion, including svMotion, and relocation must be disabled for VMs that are being imported to avoid data corruption.
// Some backup solutions explicitly prevent vMotion, storage vMotion, and relocation during backups by adding an entry to the `VPX_DISABLED_METHODS` table in vCenter.
====

0 comments on commit 40fb086

Please sign in to comment.