Powered by System Center
Removing a non-existent VMM Library Server
I admit, you don’t have to remove a non-existent VMM Library Server everyday, but today happened to be such a day. Let me explain what happened. In addition to a SQL Server 2012 AllwaysOn cluster for the VMM database and a VMM 2012 SP1 Failover Cluster, I wanted to also make the VMM Library Server highly available because the management foundation for a production Windows Server 2012 Hyper-V hosted cloud would soon become too big too fail.
Let me concentrate on the VMM Library cluster. I created an ordinary guest based 2-node Windows Server 2012 cluster using the new synthetic virtual Fibre Channel adapters, connected to an EMC VNX5300 storage system. After documenting the WWN’s and WWPNs for both adapters and requesting the SAN admin to create a few disks and to correctly zone the FC devices, creating the failover cluster was really a very quick deal. For some reason after installing EMC PowerPath 5.5 SP1, only one node of the cluster detected the correct Multi-Path Disk Device while the other thought it was dealing with a VRAID SCSI Disk Device.
Because uninstalling the devices or removing and reinstalling EMC PowerPath didn’t do the trick, I just went on to create a standard clustered file server role and add a share to be used for the VMM Library.
After some time we noticed that the cluster did not work as expected, so I decided to destroy the cluster and start over. In retrospect this was not the smartest thing to do. I should have removed the VMM Library server from VMM before I killed the cluster.
As you might have guessed, it was not possible to remove the VMM Library after I had destroyed the file server cluster. In fact I had used an identical cluster CNO (Cluster Name Object) and file server VCO (Virtual Cluster Object), which were of course different from the previous incarnation. I also manually removed the VMM agent from the cluster nodes and reinstalled them manually. Albeit to no effect.
One of my fellow MVP’s, Cameron Fuller, suggested to use PowerShell to try and forcefully remove the Library Server. I knew that was possible with a failed virtual machine, but I could not find a way in PowerShell to force the removal of a no longer existing Library Server. The old VCO was replaced by the new VCO as soon as I had recreated the failover cluster and the file server role.
I finally resorted to removing the record(s) from the VMM database. I found the procedure on this blog:
Warning: Do not start deleting records before you have a backup of the VMM database!
First find the LibraryID of the Library Server.
You cannot just delete the VMM Library records, because there are dependent records in related database tables. You must first delete the volumes used for the VMM share. Using the LibraryID found in the previous command, you can identify the volume records in the dbo.tbl_ADHC_HostVolume table.
After you have deleted the related records from the dbo.ADHC_HostVolume table, you can run this stored procedure to finally remove the VMM Server.
exec prc_ADHC_Library_Delete ‘ID’
(replace ID by the ID found in the previous commands)
After the VMM server was removed, I was able to add the file cluster again.
|Print article||This entry was posted by Hans Vredevoort on February 5, 2013 at 00:04, and is filed under Hans Vredevoort, Hyper-v, System Management. Follow any responses to this post through RSS 2.0. You can leave a response or trackback from your own site.|
No trackbacks yet.
about 2 days ago - No comments
At Inovativ, the company I work for, we more or less use Windows Azure Pack in production now. We have begun to operate as a hoster and each consultant is a tenant in our Inovativ Cloud. They can go to the Windows Azure Pack tenant portal and consume the resources we have available in our…
about 1 month ago - 4 comments
With the General Availability of Windows Azure Pack more organizations are interested in or are already implementing the complete CloudOS. Compared to the previous release Microsoft has put more effort in documentation for the product. After you have implementing your first lab environment (and you should, before trying anything like this in production) you will…
about 2 months ago - No comments
During my research for the last part of my blog series on Bare Metal Deployment I wanted to get an overview of the weights that were assigned to all virtual machines on a host. What looked like a simple thing quickly became a little complex. Let’s assume you have a Windows Server 2012 (R2) host…
System Center VMM 2012 R2 Bare Metal Deployment with Converged Fabric and Network Virtualization – Part 2 Components
about 3 months ago - 5 comments
This blog series is divided in the following parts. System Center VMM 2012 R2 Bare Metal Deployment with Converged Fabric and Network Virtualization – Part 1 Intro System Center VMM 2012 R2 Bare Metal Deployment with Converged Fabric and Network Virtualization – Part 2 Components Host Groups Logical networks and IP Pools VM Networks Uplink…
System Center VMM 2012 R2 Bare Metal Deployment with Converged Fabric and Network Virtualization – Part 1 Intro
about 3 months ago - 6 comments
Windows Server 2012 introduced a whole new spectrum of networking configurations with NIC Teaming and QoS. In previous versions the possibilities were limited but this also meant you had a limited amount of choices to make. These new features provide a huge amount of possible configurations, but it also requires you to make more decisions.…
about 5 months ago - 1 comment
Last week at TechEd I attend a session about migrating from VMware tot Hyper-V. Impressive session, which I must attend because a lot of my customers want to migrate from VMware tot Hyper-V because of the huge improvements in Windows Server 2012 Hyper-V and Windows Server 2012 R2 Hyper-V. What tools do we have to…
Connecting System Center 2012 SP1 App Controller to System Center 2012 SP1 Service Provider Foundation – 2 Scenarios
about 5 months ago - 5 comments
Recently I posted a blog series on enabling the Cloud OS with Windows Server and System Center for Hosting Service Providers that consists of the following parts Installing and configuring System Center Service Provider Foundation Installing and configuring Windows Azure for Windows Server – Part 1 Installing and configuring Windows Azure for Windows Server –…
about 6 months ago - No comments
We already know that we wouldn’t have to wait four years to get significant new features in Windows Server & Hyper-V. Looking at the list of builds since the first version of Hyper-V, we can observe there were considerable intervals between the releases of Windows Server 2008 (R2) and Windows Server 2012. We’ve seen three…
about 9 months ago - No comments
While cleaning up my mailbox, I found a note to myself dating June 2011 about a few feature requests for the next version of Hyper-V and VMM. While talking to customers throughout the year, I often hear about and collect suggestions and product improvements which I can then pass on to the Hyper-V and System…