- Hello. I have an issue with API Restore Entire VMware vSphere VM
- I have virtual Machine A with Ubuntu OS.
- I use Veeam backup to create a backup (backup 1). Next, I change the VM's OS to Debian 11. Then, I use Veeam to restore (OriginalLocation) the VM.
- The VM keeps the VM ID after the restore.
- After that, I change VM's OS to CentOS. Next, I restore (OriginalLocation) VM with (backup 1)
- There are two VMs with the same name on the VMware.
- I want to keep the VM ID when second restoring
- How can I resolve this issue?
API : https://helpcenter.veeam.com/docs/backu ... toreVmware
-
- Novice
- Posts: 3
- Liked: never
- Joined: Mar 11, 2024 2:31 am
- Full Name: zoro
- Contact:
-
- Veeam Software
- Posts: 2346
- Liked: 555 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: API Restore Entire VMware vSphere VM create new vm with restore mode OriginalLocation
Hi zoro,
I'm not quite understanding your workflow here, so few clarifying questions:
1. Just to be clear, after the second restore, instead of replacing the disks of the running original VM, it creates a new VM instead?
2. As a sanity check, is it possible that the "type" value got changed from OriginalLocation to other?
3. May I ask what the goal of the testing with changing the OS and restoring from the original backup is? Just trying to make sure I get your goal so we can advise a bit better.
4. While I'm not confident this is an API issue, just as a sanity check, do you see the same behavior doing this from the UI instead of via API? (just to narrow the focus)
I'm not quite understanding your workflow here, so few clarifying questions:
1. Just to be clear, after the second restore, instead of replacing the disks of the running original VM, it creates a new VM instead?
2. As a sanity check, is it possible that the "type" value got changed from OriginalLocation to other?
3. May I ask what the goal of the testing with changing the OS and restoring from the original backup is? Just trying to make sure I get your goal so we can advise a bit better.
4. While I'm not confident this is an API issue, just as a sanity check, do you see the same behavior doing this from the UI instead of via API? (just to narrow the focus)
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: No registered users and 3 guests