Post P2V Tasks 1

P2V does not end with migrating a Physical Server to Virtual Server  but there are certain post P2V tasks that could help in improving the performance of the converted server.  Ensure you install VMware Tools on the migrated VM without fail. Remove all unwanted hardware components from a migrated virtual server like serial ports and floppy drives. Change the CPU and memory of the VM as per requirement and do not go with default values as they reflect the resources as in the Physical Server. Physical Servers are installed with OEM drivers which are resource consuming and these drivers can be removed using Add/Remove Programs once they have been converted to VMs. I came across a HP utility that can be download from here  which can be used to remove HP PSP with a single click. One of the issue that is reported is the error when they get when try to assign IP to the migrated server –  ” The IP address XXX.XXX.XXX.XXX…” is already assigned to another adapter”. This error message is caused by Ghosted NIC Cards that are present. These are the NIC cards that are converted as part of the P2V process since they were part of the physical Server but does not show […]

Be-Aware of Hyper-V Snapshots 4

Snapshots capture a state of a Virtual Machine, data and hardware configuration. VMware ESX and Microsoft Hyper-V hypervisors provides the ability to take snapshots but the mechanism used for handling the snapshots are completely different and understanding them is very important. Recently we faced an issue in one of our test Hyper-V Server where all the machines went into a saved state. We narrowed down on the root cause and found that there was no space available on the drive hosting the VMs. When we dived further, we found that there were huge .AVHD files on one of our Virtual machine. We immediately checked the Hyper-V manager for active snapshots but there were no active snapshots. We had taken snapshots for that Virtual machine that was active for a week and then deleted the same from the Hyper-V manager.  Now some search on Google led me to Microsoft’s FAQs on Hyper-V VM Snapshot on TechNet. This is when I realized that mechanism implied by Hyper-V on snapshots is completely different from VMware ESX Server and ESX handles snapshots better than Hyper-V. So here are my key learning’s that I hope would be helpful to everyone working on Hyper-V. When we […]

Removing an Orphaned Hyper-V Host from SCVMM

We were unable to remove one of our Hyper-V hosts from SCVMM as it would throw an error stating that SCVMM was unable to communicate with the Hyper-V host . We had reinstalled the Hyper-V Server without removing it from SCVMM before the re-installation process. This left an orphaned Hyper-V host on the SCVMM . Google search led me to a Technet post which suggested to use ” -Force ” switch using the Power Shell option available in SCVMM and Voila !! We were able to remove the host from SCVMM , Finally !! Steps are pretty straight forward : Login to SCVMM Click on the Power Shell icon available on the top of the screen and use the below mentioned command ” Get-vmhost Hyper-V Hostname| remove-vmhost –force “ Please note that the above command can be used when we do not remember the Credentials for the host as well as in scenarios where the SCVMM and Host are unable to communicate. When we  use  the Force parameter, VMM does not prompt for or check credentials, and VMM does not attempt to connect to the host and uninstall the VMM agent .