From: Fabien Sirjean <fsirjean@eddie.fdn.fr>
To: pve-user@lists.proxmox.com
Subject: Migrating a 10TB VM from ESXi to PVE/Ceph
Date: Mon, 7 Sep 2026 09:08:23 +0200 [thread overview]
Message-ID: <807a9c32-cc3b-4a93-bf57-4fbce34817b6@eddie.fdn.fr> (raw)
Dear all,
After successfully migrating most of our infrastructure (300+ VMs) from
VMware ESXi to PVE, we're struggling with one last critical VM: our
BlueMind/Cyrus mail server (~800 users), with a 10TB virtual disk.
Our setup is:
Source: ESXi → Dell EMC VPLEX (FC) → Dell Unity
Target: Proxmox VE → Ceph RBD (dedicated cluster)
We tried the Proxmox ESXi importer, but I/O performance degraded so much
during the live import that the mail service could not sustain its
normal workload.
We then stopped the service to complete the migration, but the import
eventually failed after almost 3 days, forcing us to start over.
Application-level migration/synchronization is not an option, so we're
looking for a block/storage-level approach with minimal downtime.
Since the datastore ultimately resides on our FC SAN, could we bypass
ESXi entirely and temporarily present the relevant VPLEX/Unity LUN to a
PVE or migration host, mount/access the VMFS datastore read-only, and
copy/convert the VMDK directly to Ceph RBD?
Even better, is there a practical way to perform the bulk copy while the
VM is running, then only synchronize the changed blocks during the final
cutover?
Any advice or experience with direct VMFS access, VPLEX/Unity
snapshots/clones, or other approaches for this kind of migration would
be greatly appreciated.
Thanks!
reply other threads:[~2026-09-07 7:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=807a9c32-cc3b-4a93-bf57-4fbce34817b6@eddie.fdn.fr \
--to=fsirjean@eddie.fdn.fr \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox