Jump to content

Recommended Posts

Posted

I am planning in the summer to have a Storage Spaces Direct server (hopefully build the system) and then take our existing VMs from a HyperV 2012 hypervisor to a new 2016 hypervisor cluster on the storage spaces direct volume.

As we have no downtime in the summer I see it somewhat a straightforward to remove the Vm from the 2012 cluster and move it across to the 2016 cluster then upgrade integration services.

Are there any pit falls I am missing?

Darren

Posted

We've done something similar to this last holiday, and had minimal downtime.

 

You will probably want to find/make a vm to test the move process.

 

Some of the pitfalls we came across were:

* network switch name different - it prompts you for this during the move.

* VLAN settings in VM settings

* we moved some VMs from one school site to another - this required static network settings to be updated before it would talk on the network

* authentication issues between the servers. In the end, I had to remote onto the source host and kick off the move from there.

* remember to update your backup system after so the VMs are still backed up.

 

Is there any reason you aren't upgrading to 2019?

Posted

Thanks!

Indeed I think I need to bite the bullet and go with 2019.

The HyperV system is on a seperate domain to live Vms and wanted to remove the HV domain to simplify things but this maybe too much !

I think that I will go Converged rather than hyper converged as it is too difficult to plan and set in stone as I have only been in post 3 months..

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...