Hi,
I tried to use Veeam B&R (version 12.1.2.172) Enterprise Plus to replicate a Linux VM to other storage and ESXi host.
But when I boot the VM, it starts in Boot Manager only.
I also tried it with creating a new Windows Server 2022 VM and replicated it the same way, but it also starts in Boot Manager menu.
Anyone else has this experience with replicating VM's?
I used this same method before with an older version of B&R and that worked perfectly.
Regards,
Berend Schotanus
-
- Service Provider
- Posts: 11
- Liked: 3 times
- Joined: Mar 22, 2022 3:53 pm
- Full Name: Berend Schotanus
- Contact:
-
- Product Manager
- Posts: 10612
- Liked: 2855 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Issue after replicating VMware VM to other storage/host
Hi Berend
I'm not aware of any known issues like this with Veeam replication.
This forum is not technical product support. We cannot provide assistance to troubleshoot technical issues. Please respect our forum policies (in red colors when you have created this topic) and contact our customer support team to investigate all technical issues.
Thank you for understanding,
Fabian
I'm not aware of any known issues like this with Veeam replication.
This forum is not technical product support. We cannot provide assistance to troubleshoot technical issues. Please respect our forum policies (in red colors when you have created this topic) and contact our customer support team to investigate all technical issues.
Thank you for understanding,
Fabian
Product Management Analyst @ Veeam Software
-
- Chief Product Officer
- Posts: 32360
- Liked: 7719 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Issue after replicating VMware VM to other storage/host
Veeam replication creates bit-identical copies of VM images and this technology is very mature (available since V1 actually). So if these images do not boot in the target site then most likely there's a storage-level corruption or some other hardware issue resulting in silent data corruption. Our support should be able to nail it down so you could open a support case with your hardware vendor.
Alternatively, there could be something about VMs themselves (their configuration) that is unsupported by Veeam. Like physical RDM or in-guest iSCSI mounted disks usage perhaps?
Either way, a bug in Veeam replication is extremely unlikely... with high probability, it is some environment-specific issue that should therefore be diagnosed by our Customer Support team first before it makes sense to discuss on these forums.
Thanks
Alternatively, there could be something about VMs themselves (their configuration) that is unsupported by Veeam. Like physical RDM or in-guest iSCSI mounted disks usage perhaps?
Either way, a bug in Veeam replication is extremely unlikely... with high probability, it is some environment-specific issue that should therefore be diagnosed by our Customer Support team first before it makes sense to discuss on these forums.
Thanks
Who is online
Users browsing this forum: No registered users and 17 guests