Hello,
currently we are migrating some VMs from VSphere to Proxmox. This works perfectly via normal restore (thanks to 13.1) but fails with instant recovery - when we are in the "chose storage" dialog there is no storage visible at all, no matter if we select a CEPH-backed host or a host with shared FC storage.
Is this currently a limitation when restoring VSphere VMs?
Markus
-
mkretzer
- Veeam Legend
- Posts: 1351
- Liked: 493 times
- Joined: Dec 17, 2015 7:17 am
- Contact:
-
david.domask
- Product Manager
- Posts: 3961
- Liked: 962 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: VSphere VM instant recovery to Proxmox - no storages selectable
Hi Markus,
I don't see any such limitation in the supported workloads or the Storage section of the User Guide specifically relating to VMware VMs, so open a Support Case and let Veeam Support review the situation.
I don't see any such limitation in the supported workloads or the Storage section of the User Guide specifically relating to VMware VMs, so open a Support Case and let Veeam Support review the situation.
David Domask | Product Management: Principal Analyst
-
mkretzer
- Veeam Legend
- Posts: 1351
- Liked: 493 times
- Joined: Dec 17, 2015 7:17 am
- Contact:
-
jbender81
- Influencer
- Posts: 11
- Liked: 4 times
- Joined: Jul 09, 2026 9:33 am
- Full Name: Jörg Bender
- Contact:
Re: VSphere VM instant recovery to Proxmox - no storages selectable
Hi,
I noticed the same issue.
We have no file based storage set up to host virtual machines, just for snippets, templates and ISO files.
My assumption is, that instant recovery requires a file based final destination, as itself is probably emulating qcow2 during instant recovery and is not able to migrate to raw.
Was perchance one of the available storages a file based storage?
We had not yet time, to test this assumption.
Cheers
Jörg
I noticed the same issue.
We have no file based storage set up to host virtual machines, just for snippets, templates and ISO files.
My assumption is, that instant recovery requires a file based final destination, as itself is probably emulating qcow2 during instant recovery and is not able to migrate to raw.
Was perchance one of the available storages a file based storage?
We had not yet time, to test this assumption.
Cheers
Jörg
Who is online
Users browsing this forum: Google [Bot], homerjs and 75 guests