How to make optimal use of Hyper-V?

[Dewei]

SQL and virtualization specialist guys does Hyper-V now almost with VMware's ESX server. I have heard that for maximum performance and avoid unnecessary administrative burdens, there are some tips. I am here to get some tips about the making optimal use of Hyper-V. I am sure that you members must be knowing about it. Any small tip could be useful for me, so please post any (useful) tip.

[Kanakpriya]

Before migrating a VM between two platforms, one should remove all VM-specific tools and drivers for the guest while it is still on the old virtual hardware. After the move, this is also not longer or only possible with considerable additional effort. The safest way to migrate VMs from one Hyper-V host to another, is to use the Export-/Import-Function. Live migration requires more extensive requirements that can not also have to make considerable effort and can only. For backup of Hyper-V machines can use Windows Backup, but you must previously the writer of Hyper-V with Windows Server Backup register VSS.

[Umberto-Micro]

If you consolidate its server environment using Hyper-V, it is a good idea to the appropriate virtual machines in the Windows Server Backup with and for them as regularly to ensure automatically. By default, this is not the case. Thus, the Hyper-V machines with Windows Server backup can be integrated, it is necessary, Writer of Hyper-V with Windows Server Backup to register the VSS. The VSS writer ensures that the used VHDs consistent state in the shadow copy of the volumes are stored in one, even if they are currently in use. Also the backup server using Windows Backup with downtime for the virtual server is connected, except they run on Windows Server 2003 or Windows Server 2008 (R2). Also, to configure Windows Server 2008 with the registration of the Hyper-V VSS writer backup of all virtual machines, the selection of individual VMs is not possible. This can only WSB on Windows Server 2008 R2.

[Barsha]

I have heard that for maximum performance and avoid unnecessary administrative burdens, there are some tips. I am here to get some tips about the making optimal use of Hyper-V.

The number of physical network adapter must be addressed by the VMs, not avoided by the hosts to the risk of bottlenecks. Storage and access to them are a major challenge for any virtualization strategy. Ideally, there is even a physical network adapters per VM. Hyper-V can be done without SCVMM Powershell to administer if the PowerShell management Library for Hyper-V installed. It is used by Microsoft CodePlex offered for download and is open source. With Hyper-V R2 is the performance of dynamic virtual disk with the virtual disks of fixed size to be comparable, so it is not longer necessary, therefore resorting to the latter from.

[Liliana]

Here are some more tips. Direct launch the VM from an iSCSI LUN: This binds to the first LUN on the Hyper-V host. Then to set up the VM without first a hard disk, then select the IDE controller and adds a hard drive. Here then is the included iSCSI LUN is available. Processor Compatibility note: The live migration between two Hyper-V hosts without downtime of the VM must be their processors from the same manufacturer and same here by the family. To migrate a VM at all live to a host with a different processor, you have to turn in their settings that option. Direct access to iSCSI SANs from the VM: This is used in the guest's iSCSI initiator from Start Menu "Administration".