Feature request (move vm)

[MAA]

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).

[Mildur]

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.

[MAA]

My request for Move(Migration), not for Replication.
Replication create clone of VM (and clone have different name). I do not need two VM.

[soncscy]

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.

[MAA]

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?

[Mildur]

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.

[soncscy]

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.

[MAA]

Do you use one vcenter for all datacenters? Or are the vcenter and hosts independent from each location?

We have one vCenter server.

[Mildur]

Why not using a scheduled task from the vcenter to move the vm after midnight?

https://docs.vmware.com/en/VMware-vSphe ... 115F4.html

[MAA]

why are you asking? other options have been considered and they are not suitable.

[soncscy]

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?

[MAA]

Why not? what part is missing?
it's in the first post: possibility of a final switch manually

[soncscy]

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.

[MAA]

Apparently, you absolutely do not understand what the essence of my feature request is

[soncscy]

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.

[TaylorB]

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.

[MAA]

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.

I tried replication, but after that I found:
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..

[PetrM]

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!

[MAA]

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.

[PetrM]

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!