Features lost when using VMware instead of HyperV:
You'll lose "HyperCache" HyperCache uses RAM to cache the most common disk IO for a HyperV template. This speeds up the VM due to fewer real read/writes from the disks. When working effeciently, this is a big performance boost. Especially if your physical disks are slow.
Your question "I’m going to face different challenges such as Pooled VDI on Hyper-v using disk referencing where the parent setup intend and the child VMs are linked to small disk file? Is this still the case with VMWare..?"
Yes, VMware has "Linked Clones" this works in a very similar way. eg, Parent VM (That you use as a template) Child VMs (That you use as VDI) the Child VM works in the same way as a snapshot, it only records the changes so the disk size can be very small.
You could always leave your SQL where it is.
However, if you search the KB we have a good migration guide.
Transition SQL Clustering from Hyper-v to VMWare will be a challenge.. Convert vhd to VMDK... that's to risky spending time in resolving compatibility issues such as P2V cleanup or other unknown issues.
Will that be simple for vWorkspace architecture to be mapped to the same DB on different SQL Cluster instance..? Instead will take this approach...
Build fresh SQL Cluster in VMWare Environment.
Ensure all best practices of Virtualization SQL applied.
Export Databases.
Import them into the new SQL Cluster.
Map vWorkspace ODBC to the new SQL Instance.
Off course this activity will be done at last once all servers of other roles of vWorkspace implemented onto the existing SQL Instance.
DELL-Andrew W1
378 Posts
0
April 15th, 2016 10:00
Hi,
Features lost when using VMware instead of HyperV:
You'll lose "HyperCache" HyperCache uses RAM to cache the most common disk IO for a HyperV template. This speeds up the VM due to fewer real read/writes from the disks. When working effeciently, this is a big performance boost. Especially if your physical disks are slow.
Your question "I’m going to face different challenges such as Pooled VDI on Hyper-v using disk referencing where the parent setup intend and the child VMs are linked to small disk file? Is this still the case with VMWare..?"
Yes, VMware has "Linked Clones" this works in a very similar way. eg, Parent VM (That you use as a template) Child VMs (That you use as VDI) the Child VM works in the same way as a snapshot, it only records the changes so the disk size can be very small.
You could always leave your SQL where it is.
However, if you search the KB we have a good migration guide.
Thanks, Andrew.
Habibalby_083114
68 Posts
0
April 8th, 2016 10:00
Transition SQL Clustering from Hyper-v to VMWare will be a challenge.. Convert vhd to VMDK... that's to risky spending time in resolving compatibility issues such as P2V cleanup or other unknown issues.
Will that be simple for vWorkspace architecture to be mapped to the same DB on different SQL Cluster instance..? Instead will take this approach...
Off course this activity will be done at last once all servers of other roles of vWorkspace implemented onto the existing SQL Instance.
Any thoughts...?
Regards,
Habibalby_083114
68 Posts
0
April 16th, 2016 22:00
Hi Andrew,
Thank you very much for your reply, will search the KB and post back my findings and final plan.
Regards,
DELL-Andrew W1
378 Posts
0
April 18th, 2016 04:00
Hello,
Here is the KB https://support.software.dell.com/vworkspace/kb/61702
The 2nd attachment is more up to date on SQL versions. It doesn't cover clusters so you'll need to figure that part out though I'm afraid.
Thanks, Andrew.