Veeam replication not honoring changed dynamic max memory?

[loelly]

So, I've got a Linux virtual machine running on Windows Server Hyper-V 2012 R2 and being replicated to another Server 2012 R2 using Veeam v8. The virtual machine is configured to use dynamic memory. Now I changed the value for maximum memory on the VM from 2 GB to 4 GB and would expect Veeam to detect this change and to configure the replica VM accordingly, but it doesn't, it stays at 2 GB on the destination host.

Is this a known limitation? Any chances this will change in the future?

[foggy]

Maik, this is a known issue that will be addressed in the upcoming Veeam B&R v8 Update 2.

[loelly]

It looks like this has not yet been fixed, am I right?

[veremin]

Are saying that you've already updated to Update 2b and the said problem still persists?

[loelly]

Damn. I just noticed I'm still running Update 1 on that machine. Will let you know on Monday. Thanks!

[loelly]

So, after upgrading to Update 2b, the job no longer fails but dynamic min and max memory is set to startup memory, which is a bad thing (= bug). Veeam should put the exact same memory options to the replica as the original virtual machine (was so before Update 2b).

EDIT: opened case /w support, ID 00975178.

[foggy]

Maik, this is actually another issue that is scheduled to be addressed in v9. The original issue (not syncing dynamic memory changes) was addressed in Update 2.

[loelly]

Thanks for letting me know Alex!