feature request - failback state transfer

[mcz]

Hi everybody,

I'm wondering why the current state plus RAM can be transferred between the operation "Instant Recovery" and "Quick Migration" but not between replication failover and failback.
I mean you can always divide between failover and planned failover but in case of planned failover I would appreciate the ability to just suspend the source machine, transfer the state to the target vm and resume on target exactly on the spot where the vm has been suspended before.

Thank you!

[foggy]

...in case of planned failover I would appreciate the ability to just suspend the source machine, transfer the state to the target vm and resume on target exactly on the spot where the vm has been suspended before.

This is exactly what is done during planned failover.

[mcz]

...not really because vm will be shutdown on planned failover, it will not be suspended....

[foggy]

Why would you like it to be suspended instead of switched off?

[jsprinkleisg]

I like the idea. This option would potentially enable a shorter disruption during the planned failover, assuming the destination hosts' CPUs and EVC mode are compatible and no network changes are required. As Michael noted, Veeam already provides similar functionality for Instant Recovery and Quick Migration, so I suspect it wouldn't require a great deal of dev effort to add this option.

[mcz]

Why would you like it to be suspended instead of switched off?

...well I think there are many reasons but to make it short, it would actually has the same affect as if you do a vMotion and I'm sure I don't have to tell you why it's so cool. And as mentioned, this ability is still implemented between Instant Recovery and Quick Migration.

Hope it is clear now.

[foggy]

Ah, now I got it, sorry. Suspend, sync to the suspended state, and resume on target.

[mcz]

Exactly! You explained my very long story in a short way, I like it