just another private tech blog
The VMware Labs engineers built a fling to migrate a vCenter Server installed on a Windows Server to the vCenter Server Appliance.
For me the greatest limitation is that Windows Server 2012 a higher isn’t supported yet. Because of “winexe-bug” the migration appliance could not get the data from the source machine. William Lam told me that the engineers know about this issue and hopes that it would be fixed soon.
For all of you who could not wait… maybe I’ve a workaround.
After testing a new installation of vCenter 6.0 in my nested environment at work I wanted to test the upgrade from 5.5 to 6.0.
I was thinking all settings for database roles, users and schema which were good enough for the installation of 5.5 would be okay for 6.0. But first the install guide says “no”. So I’ve checked all settings in my database and added missing ones. We use VC_Admin and VC_User roles instead of DBOwner because best practise of VMware recommend this as way #1
I wanted to set
GRANT EXCUTE ON msdb.dbo.sp_lock TO VC_ADMIN_ROLE
Here I get the first failure. SP_LOCK is not a dbo-procedure but a sys-procedure. So you can set this permission only on master and not on msdb database. I’ve set this permission via GUI, but I think this will not fix my problem.
All packages,except vCenter Server, gets updated successfully. Nearly to the end of the vCenter Server Update I get an error while updating the database and the installation gets removed.
After the I’ve changed the DB Roles to DBOwner for vpxuser in msdb and vcdb.
With these settings I could update the vCenter Server.
Almost everythings worked as it should. The only problem was Backup Exec 2015. None of the “old” and functional backup jobs or newly created one time backups could create a snapshot over the vCenter Server. For this problem you find my blogpost here http://blog.ganser.com/666.
Related documents:
vSphere 6.0 Documentation
vSphere 6.0 Documentation – Prepare Database
Today I’ve upgraded our vCenter Server from 5.5 to 6.0. Our BackupAdmin has upgraded the Backup Server one week before and all worked fine.
The upgrade on my nested vSphere test environment works fine too. The backup and restore tests runs over the vCenter 6 with all the ESXi 5.5 and 6 servers. *damn*
Now in our production environment the upgrade runs an all services works. After starting the test backup for one virtual machine i get the following error:
Job ended: Wednesday, 17 Jun 2015 at 9:03:05 PM Completed status: Failed Final error: 0x200095bf - A failure occured while locking the virtual machine in place for backup/restore operations. Final error category: Resource Errors For additional information regarding this error refer to link V-79-8192-38335
Update 30.10.2015:
With Backup Exec 15 revision 1180 Feature Pack 1 the problem could be solved. Thx to Alex Millà for his comment. I also could reproduce it in my environment and the error is away.
puh! – VCP-NV done
I’ve passed the VCP-NV exam. This exam was a new level for me. I’ve never spend so much attention to the virtual network and its bindings to the physic. The prep for this exam showed me the advantages and complexity of the vDS and NSX. Maybe we upgrade the version to enterprise to get the vDS features.
The following steps / tips I want to give you for your way to VCP-NV
Continue reading
In my last training Fabian Lenz and I discuss pro and con of power management in ESXi.
We thought DPM is mostly used in VDI-environments. In those environments the savings would be the best, because the virtual desktops didn’t work at night and many of the ESXi hosts could be powered off. But DPM ist not the only thing which affects the power consumption. ESXi could use ACPI C- and P-States from the CPU to control the power of the physical cores. Fabian experiements with a bigger VDI environment and gets interessting informations with activated DPM (watch his blog).
© 2025 gansercom
Theme by Anders Noren — Up ↑