Upgrade VM Configuration Version on replication Hyper-v

[hauer@sysdat.at]

Initial config:

2 Hyper-v Host with server 2012 one of them for replication

Then 2 new hosts with server 2016

Alle vm's moved to the new boxes. Create the replication job and all workes well without cbt because the VM's are on Version 5

Then changed the version on the primary box to version 8.

All works well but

If i look at the replication server the vm-version is still 5.

Should Veeam not update the configuration? Or should i? or should i recreate the replica?

Thanks Wolfgang

[foggy]

Hi Wolfgang, HW version is not automatically updated on target. You can try to do it manually, should work.

[hauer@sysdat.at]

thanks, i will try

Wolfgang

[Blue407]

Morning all

I have a hyper-v cluster running server 2016, each blade was individual rebuilt, one at a time until they were all done and then the cluster version was updated.

My B&R server is also a hyper-v host, containing a replica of the live VM's from the cluster, these were created and maintained by Veeam Replication. This server was in-place upgraded from 2012 R2 to 2016.
I have an additional off-site backup server, with its on repository and also another Replica of the cluster VM's, this was built natively with server 2016.

After I upgraded the cluster, I stopped each VM and upgraded its integration services to the latest one. On all Hyper-V hosts, each VM is shown as Configuration Version 8.0

I noticed a couple of days ago the the Replica VM's on my 2016 B&R server are still at Configuration Version 5.0. In my head, each Replica VM is kept up to date with changes from the original source VM, so I would have expected the configuration version to also replicate.
I double checked the off-site server and this also shows v5.0

Is this expected behavior, a bug?

I'm guessing as the replica VM's are stopped, I could upgrade their Configuration Version, but should I have to?

[Mike Resseler]

Paul,

Sorry for my late answer. I am not 100 percent sure, but I would believe it is expected behavior (to make sure you can do rollbacks to another version in case of a cluster rolling upgrade). I will check with some people and try to get back to you with the correct answer

Thanks
Mike

[Blue407]

If that is the case, at what point would it replicate the latest version?

And, would the only way to update it be to delete the Replica and do a new replication so that all settings are replicated from scratch?

[foggy]

Hi Paul, yes, this is expected behavior. No need to delete replica, you can just change its configuration version manually.