In our company, our major productive servers are hosted in vSphere as Windows-based virtual machines. Some of them need very big disks. Through the largest disk space supported in vSphere is 16TB (or maybe more, i dunno), I’m not interested to create such a big file in VMFS. It will be really a pain your *** when you have to move such a big file among datastores, even among data facilities by using portable hard drives.
Creating smaller disks instead of a big one for every Windows-based VM, IMHO.
Fortunately, Windows support to merge small disks as a big one, using dynamic disk function. There are 4 kinds of volume can be supported in such a condition: Spanned, Striped, Mirrored and RAID-5. You can consider them like JBOD, RAID-0, RAID-1 and RAID-5 functions in a simple legacy storage device.
Because data protection is existed in the SAN, Mirrored and RAID-5 volumes are not considered at all. Striped will make it a little faster when lots of virtual disks fight for limited IOPS resources within one datastore. But there is no way to extend any stripped volume (https://technet.microsoft.com/en-us/library/cc770938.aspx).
So, the useless volume format in a traditional world, spanned volume, is the best solution, maybe the only one. Next time when you need to create big virtual disks for Windows in any virtualization environment, don’t forget to consider using Spanned Volumes.
Due to the removal of P2V wizard in SCVMM 2012 R2, we need to to this migration manually.
In this scenario, we will move a Windows Server VM hosted in vSphere/ESXi 6 to SCVMM/Hyper-V 2012 R2.
- Administrator account with password of the VM to be moved.
- A working SCVMM 2012 R2 with Hyper-V, and the client tool for management.
- A working vSphere 6 with ESXi, and the client tool for management.
- A network shared folder which can be accessed with read-write permission by VM, Hyper-V (optional) and the computer which the client tool of SCVMM located.
Here are the steps:
- Download the tool disk2vhd from https://technet.microsoft.com/en-us/sysinternals/ee656415.aspx and decompress it into the network shared folder.
- Log into the VM, check these settings:
IP Address. If it’s set to automatic, make announce to your network admin to either set the VM to fixed IP address, or rebinding the MAC address later.
- System CPU and memory.
- OS Release name and bit wide, e.g. Windows Server 2008 Standard 32bit.
- Hard disks and partitions structure.
- Run the disk2vhd at the network shared folder from VM. I suggest you not to copy it to the VM. All partitions which belong to the same hard disk should be exported to the same file at the SAME time. And all partitions from different disk should NOT be in the same exported file.
For the VM running Windows Server 2003 (R2 included, x86 x64 included), do NOT check the option for virtual-pc. It will prevent the success from installing Hyper-V integration services.
This step may take a while.
- Create a new VM in SCVMM by using the correct name, CPU, memory, OS release name. For my test, I cannot create a VM without hard drive. So just delete it after the creating finished.
- Copy the file(s) created from step 3 into the folder of the new VM.
Due to the Windows bug of calculating free space of the host drive instead of the cluster volume disk, you may be prompted with an error said no enough disk space left for the VHD files.
In this case, you need to execute the copy from Hyper-V, not form another computer. If your Hyper-V is installed without the full OS, aka Windows Hyper-V Server, you may have to do this by using cmd. The command for mapping a network shared folder as a driver is:
net use x: \\path\to\your\shared\folder
If you need to specify the account for accessing that folder:
net use x: \\path\to\your\shared\folder password /User:domain\account
After VHD files copying, use this to unmap the folder:
net use x: /d
- Adding the VHD files to the new created VM by correct sequence.
- Shutdown the old VM and boot the new one.
- Log into the new VM, uninstall the VMware tools and shutdown the OS. If your VM is using Windows Server 2003 and you are using Remote Desktop to access SCVMM, now you have to use keyboard to finish this job.
- Install Hyper-V integration services. For Windows Server 2012 and above, it’s optional but recommended. For Windows 2008 R2 and previous, it’s necessary.
- Start the VM again and set the IP addresses of network interface cards.
- Mark or remove the old VM for avoiding conflicts.
Hope this work-though helps.
In one datacenter of my company, there was a strange problem last month of VMware vSphere.
Here is our structure:
SqlServer instance for vSphere is installed dedicated on cluster server. SqlServer version is 2012 Enterprise and Windows is 2012R2 Standard
vCenter is installed on another server.
After we applied July patches from Microsoft and restart the vCenter server, nearly all services from VMware cannot start. In event viewer, one event said:
The VMware Inventory Service service terminated with the following service-specific error:
As the request from VMware support, I uninstalled all updates related and reboot but it won’t help. I thought there may be some error related to the database connection. I ran the connection test from ODBC setup window, test finished succeeded. So I collected and submitted the log file generated from vCenter server command line. You know it’s really huge.
2 weeks later, I got an email from the high level engineers of VMware. By digging the log, they found that the vCenter cannot connect to SqlServer and the tcp service port is specified. At that moment, thanks to documentation I wrote :), I found that tcp service port is different than it should be. When I checked the SqlServer, I found the reason really weird: the TCP port of this instances is modified, automatically and silently. Due to I really used vSphere client just before upgrading Windows, I’m quite sure this issue is related to at least one of the patch which applied on the database cluster, launched by Microsoft in July 2016. And after a search, there is another instance of SqlServer which has the port changed. Due to the port changed and our firewall policy is set based tcp port, the client, vCenter in this issue, cannot connect to this SqlServer instance. After the port setting changed back and instance restarted, vCenter is back to normal.
Don’t ask me why ODBC test passed without any problem. If you know the answer, I’m listening as well.
This is a record for upgrading vSphere 5.5 to 6. In this scenario, database for vCenter is a powered by SqlServer on a dedicated server.
Phase 1: Prepare
- Before upgrading, something need to be ready.
- Password of vCenter domain account.
- Password of vCenter SSO.
- ISO files for vCenter and ESXi. These files should be tested by checking MD5 or SHA hash codes.
- License Keys. vCenter and ESXi keys can be gotten from VMware site by upgrading the currents.
- vCenter server and databases should be backed up.
- vSphere Update Manager Client (not server side) and vSphere Client should be uninstalled.
Phase 2: Upgrade vCenter
Mount the ISO of vCenter and perform the upgrading. Passwords of SSO and account will be required by this process.
The current instance of vCenter will be detected by setup program and all settings will be preserved. Current settings will be exported and will be imported automatically but not be removed after.
This step will need more than 1 hour.
At the end of this process, the post upgrade steps will be prompted including entering new license key and deleting the exported setting folder. You have to wait several minutes for web client service initializing. This is a good time for upgrading Update Manager Server and PowerCLI.
Phase 3: Install vSphere Client
Install vSphere Client and Update Manager Extension. If database error is occurred in extension installing, you need to check the account for running the VMware vSphere Update Manager Service. It should be a domain account but will be replaced to system account by setup process incorrectly.
Phase 4: Upgrade VM tools
You have to upgrade all VM tools one by one.
Although there are many official documents about vSphere 6 launched recently, the release date of this product is still not uncovered.
One sure thing is there will be a new product, vFabric Postgres database, to replace the SQL server express database. The external database is still supported as well.
I will post a workthough for upgrading after it launched.
After a clean installation process, firewall of Hyper-V Server is set to deny any remote connection by default.
If you need to management other than using console, you may want to enable inbound rules for Remote Management and Remote Desktop by running these commands in the console.
To enable the Remote Management:
cscript C:\windows\system32\scregedit.wsf /im 1
To enable the Remote Desktop:
cscript C:\windows\system32\scregedit.wsf /ar 0
And, you need to enable the remote desktop from the sconfig (the blue console window) also.
Microsoft provides a new way to activate VMs hosted in Hyper-V, named Automatic Virtual Machine Activation (AVMA). It makes the activation step of VMs much easier.
- Hypervisor: Windows Server 2012 R2 Datacenter with Hyper-V role. Other versions are not supported. Dedicated Hyper-V Server is not supported.
- VM: Windows Server 2012 R2 Datacenter, Standard and Essentials.
- Prepare and activate your Hypervisor;
- Install supported OS as VM with the key listed below, or change the key of an installed VM with command “slmgr /ipk <key>”.
- Windows Server 2012 R2 Datacenter: Y4TGP-NPTV9-HTC2H-7MGQ3-DV4TW
- Windows Server 2012 R2 Standard: DBGBW-NPF86-BJVTX-K3WKJ-MTB6V
- Windows Server 2012 R2 Essentials: K2XGM-NMBT3-2R6Q8-WF2FK-P36R2
These keys are supported to being used in any unattend.exe setup file also.