any issues by replicating vm from 2012 to 2016 hyper-v? how will new guest services impact network card etc.?
My logic says it will impossible to fallback from 2016 to 2012 though, but as a transfer method from a 2012 failover cluster to a new 20216 failover cluster i was wondering if veeam is better to use than just copy all .vhdx files and create new vms.
-
- Service Provider
- Posts: 1092
- Liked: 134 times
- Joined: May 14, 2013 8:35 pm
- Full Name: Frank Iversen
- Location: Norway
- Contact:
-
- Chief Product Officer
- Posts: 31802
- Liked: 7298 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: replicate fo hyper-v 2012 to hyper-v 2016
Correct - 2012 to 2016 will work fine, but not the other way around. Thanks!
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: replicate fo hyper-v 2012 to hyper-v 2016
As additional information. Any reason why you are not considering Rolling-Cluster upgrade?
-
- Service Provider
- Posts: 1092
- Liked: 134 times
- Joined: May 14, 2013 8:35 pm
- Full Name: Frank Iversen
- Location: Norway
- Contact:
Re: replicate fo hyper-v 2012 to hyper-v 2016
as far as i know this is not supported from 2012 to 2016, only from 2012 R2 to 2016.
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: replicate fo hyper-v 2012 to hyper-v 2016
Frank,
You are absolutely right. I didn't realize you were talking about 2012. My mind made it automatically R2 I'm afraid
You are absolutely right. I didn't realize you were talking about 2012. My mind made it automatically R2 I'm afraid
Who is online
Users browsing this forum: No registered users and 25 guests