-
- Expert
- Posts: 101
- Liked: 3 times
- Joined: Apr 27, 2013 12:10 pm
- Contact:
Feature request (move vm)
Hello,
We need a way to move (migrate) the VM (to another host in another subnet/dc/city/country), but with the possibility of a final switch manually (due to the fact that the final switching is possible only after the end of the working day).
We need a way to move (migrate) the VM (to another host in another subnet/dc/city/country), but with the possibility of a final switch manually (due to the fact that the final switching is possible only after the end of the working day).
-
- Product Manager
- Posts: 9846
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Feature request (move vm)
Hi Maa
Veeam Replicas can be used with planned failover after work hours. To finalize the move use permanent Failover.
1. Create a replica Job
2. Replica Job replicates the vm from the original host to the other location/host
3. do a Planned Failover outside of your production hours
4. finalize it with a permanent failover
Is use this all the time when I need to migrate vms between two VmWare environments.
Veeam Replicas can be used with planned failover after work hours. To finalize the move use permanent Failover.
1. Create a replica Job
2. Replica Job replicates the vm from the original host to the other location/host
3. do a Planned Failover outside of your production hours
4. finalize it with a permanent failover
Is use this all the time when I need to migrate vms between two VmWare environments.
Product Management Analyst @ Veeam Software
-
- Expert
- Posts: 101
- Liked: 3 times
- Joined: Apr 27, 2013 12:10 pm
- Contact:
Re: Feature request (move vm)
My request for Move(Migration), not for Replication.
Replication create clone of VM (and clone have different name). I do not need two VM.
Replication create clone of VM (and clone have different name). I do not need two VM.
-
- Veteran
- Posts: 643
- Liked: 312 times
- Joined: Aug 04, 2019 2:57 pm
- Full Name: Harvey
- Contact:
Re: Feature request (move vm)
What you're asking is a bit unusual MAA; the idea is clear, but you are basically asking for a replica that cleans up the original.
Migration isn't the right term here because I'm assuming you want to keep the original running while the migration occurs, right?
If that's the case, use Replica to do this and script cleaning up the original virtual machine once the Permanent Failover occurs. This is the best solution for you.
Migration isn't the right term here because I'm assuming you want to keep the original running while the migration occurs, right?
If that's the case, use Replica to do this and script cleaning up the original virtual machine once the Permanent Failover occurs. This is the best solution for you.
-
- Expert
- Posts: 101
- Liked: 3 times
- Joined: Apr 27, 2013 12:10 pm
- Contact:
Re: Feature request (move vm)
We need the VM to keep its name and ID after moving (in fact, it must be the same VM)
Are these requirements met when using Replication+PermanentFailover?
Are these requirements met when using Replication+PermanentFailover?
-
- Product Manager
- Posts: 9846
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Feature request (move vm)
Do you use one vcenter for all datacenters? Or are the vcenter and hosts independent from each location?
If each datacenter and esxi host uses their own vcenter or no vcenter at all, VM ID will also change when you move the vm. VM MoRefID will only be preserved in the same vcenter environment or on the same ESXI Host.
If each datacenter and esxi host uses their own vcenter or no vcenter at all, VM ID will also change when you move the vm. VM MoRefID will only be preserved in the same vcenter environment or on the same ESXI Host.
Product Management Analyst @ Veeam Software
-
- Veteran
- Posts: 643
- Liked: 312 times
- Joined: Aug 04, 2019 2:57 pm
- Full Name: Harvey
- Contact:
Re: Feature request (move vm)
Fabian is correct on the MorefID.
What is the use case for the MorefID requirement? For continuing backup chains?
I'm kind of curious why you aren't doing this at the VMware level and trying to orchestrate it at the backup application level; Vmware can do this with vMotion, and you can have "on-demand" migrations pretty fast. Wouldn't it make more sense to just configure that? It's the correct technology for this.
What is the use case for the MorefID requirement? For continuing backup chains?
I'm kind of curious why you aren't doing this at the VMware level and trying to orchestrate it at the backup application level; Vmware can do this with vMotion, and you can have "on-demand" migrations pretty fast. Wouldn't it make more sense to just configure that? It's the correct technology for this.
-
- Expert
- Posts: 101
- Liked: 3 times
- Joined: Apr 27, 2013 12:10 pm
- Contact:
-
- Product Manager
- Posts: 9846
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Feature request (move vm)
Why not using a scheduled task from the vcenter to move the vm after midnight?
https://docs.vmware.com/en/VMware-vSphe ... 115F4.html
https://docs.vmware.com/en/VMware-vSphe ... 115F4.html
Product Management Analyst @ Veeam Software
-
- Expert
- Posts: 101
- Liked: 3 times
- Joined: Apr 27, 2013 12:10 pm
- Contact:
Re: Feature request (move vm)
why are you asking? other options have been considered and they are not suitable.
-
- Veteran
- Posts: 643
- Liked: 312 times
- Joined: Aug 04, 2019 2:57 pm
- Full Name: Harvey
- Contact:
Re: Feature request (move vm)
Why not?
Again, based on your needs, vMotion is what you actually want here as based on what you wrote it meets all your needs; what part is missing?
Again, based on your needs, vMotion is what you actually want here as based on what you wrote it meets all your needs; what part is missing?
-
- Expert
- Posts: 101
- Liked: 3 times
- Joined: Apr 27, 2013 12:10 pm
- Contact:
Re: Feature request (move vm)
Why not? what part is missing?
it's in the first post: possibility of a final switch manually
it's in the first post: possibility of a final switch manually
-
- Veteran
- Posts: 643
- Liked: 312 times
- Joined: Aug 04, 2019 2:57 pm
- Full Name: Harvey
- Contact:
Re: Feature request (move vm)
MAA, it's the closest you're going to get.
There's nothing that really does what you want right now, which is basically gradual migration. Do you need to move the storage also or just the compute resource?
If it's the compute resource, there's no reason vMotion won't help here.
For Storage vMotion if you have a fast enough network it should be fine and it will be "manual" whenever you decide to vMotion.
There's nothing that really does what you want right now, which is basically gradual migration. Do you need to move the storage also or just the compute resource?
If it's the compute resource, there's no reason vMotion won't help here.
For Storage vMotion if you have a fast enough network it should be fine and it will be "manual" whenever you decide to vMotion.
-
- Expert
- Posts: 101
- Liked: 3 times
- Joined: Apr 27, 2013 12:10 pm
- Contact:
Re: Feature request (move vm)
Apparently, you absolutely do not understand what the essence of my feature request is
-
- Veteran
- Posts: 643
- Liked: 312 times
- Joined: Aug 04, 2019 2:57 pm
- Full Name: Harvey
- Contact:
Re: Feature request (move vm)
It's understood for sure, just I don't think it's a realistic request Options have been given, but again, this isn't quite as straight forward as you make it.
Anyways, hope there's luck for it.
Anyways, hope there's luck for it.
-
- Enthusiast
- Posts: 92
- Liked: 14 times
- Joined: Jan 28, 2011 4:40 pm
- Full Name: Taylor B.
- Contact:
Re: Feature request (move vm)
Veeam migration makes a snapshot, records changes, and then powers off the VM on the source side, copies the delta files to the destination and then powers it up on the destination side. This only takes seconds if it happens immediately after the snapshot and you have a fast connection, as only a few MB of changes had time to occur. If you had a delayed failover time, that snapshot delta would keep building and building while you leave source in production. Then it would have to power off the VM, wait while it copies now multiple GB (maybe 10s or 100s of GB if it is a busy server) over your WAN, and then it can power on the remote side. You'd end up having a lot of downtime and it would not be a "live migration" by any means.
So I would say you probably don't actually want what you are asking for. Have someone log in at end of business and do a manual quick migration in real time.
So I would say you probably don't actually want what you are asking for. Have someone log in at end of business and do a manual quick migration in real time.
-
- Expert
- Posts: 101
- Liked: 3 times
- Joined: Apr 27, 2013 12:10 pm
- Contact:
Re: Feature request (move vm)
I tried replication, but after that I found:Mildur wrote: ↑Mar 09, 2022 7:16 pm Hi Maa
Veeam Replicas can be used with planned failover after work hours. To finalize the move use permanent Failover.
Is use this all the time when I need to migrate vms between two VmWare environments.
1) VM name changed
2) VM ID changed
because of this, backups jobs stopped working.
thus, the option with replication is absolutely unacceptable.
I continue to wait for a response to my feature request from the Veeam staff..
-
- Veeam Software
- Posts: 3626
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Feature request (move vm)
Hello,
If I get it right, the request is to make Quick Migration with the possibility to schedule switchover. I think it's an interesting idea, on the other hand I cannot say that I see this request quite often. Thus, I can note the request but cannot provide any ETA.
Thanks!
If I get it right, the request is to make Quick Migration with the possibility to schedule switchover. I think it's an interesting idea, on the other hand I cannot say that I see this request quite often. Thus, I can note the request but cannot provide any ETA.
Thanks!
-
- Expert
- Posts: 101
- Liked: 3 times
- Joined: Apr 27, 2013 12:10 pm
- Contact:
Re: Feature request (move vm)
PetrM
possibility to schedule switchover
not on schedule, but manually (due to the fact that it is impossible to predict how long it will take for a terabyte-sized VM to move over the Internet)
also please add the ability to Re-IP for such moves.
possibility to schedule switchover
not on schedule, but manually (due to the fact that it is impossible to predict how long it will take for a terabyte-sized VM to move over the Internet)
also please add the ability to Re-IP for such moves.
-
- Veeam Software
- Posts: 3626
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Feature request (move vm)
Ok but I think that both manual and scheduled switchover options would be fine. Anyway, I cannot guarantee that it will be included in future releases but I noted your request.
Thanks!
Thanks!
Who is online
Users browsing this forum: G_Mellor and 52 guests