vcenter

Can I protect my vCenter Server with vSphere Replication?

Duncan Epping · Sep 21, 2012 ·

Someone asked this question last week when I posted my “back to basics” vSphere Replication blog. I guess protecting vCenter Server isn’t too difficult but how about recovering it after a failure?

Those who have used vSphere Replication know that you need vCenter Server to click “Recover”. In a dual vCenter Server configuration that is not a problem. But what if you just want to protect your vCenter Server virtual machine and replicate it to a second piece of storage. I tested this and then “killed” my vCenter Server. How do I get my vCenter Server up and running again from this replica?

Let me start by saying that this is unsupported as far as I know. So lets start by checking the folder in which the replica of the vCenter Server resides:

  8.5K Sep 21 09:46 hbrcfg.GID-d69c6cad-42a5-474a-86c4-c3158d1a3b42.6.nvram.18
  3.4K Sep 21 09:46 hbrcfg.GID-d69c6cad-42a5-474a-86c4-c3158d1a3b42.6.vmx.16
   267 Sep 21 09:46 hbrcfg.GID-d69c6cad-42a5-474a-86c4-c3158d1a3b42.6.vmxf.17
124.0K Sep 21 09:46 hbrdisk.RDID-9786ae39-cd3a-4773-be63-cd1bc3641d59.14.175750085646519-delta.vmdk
   379 Sep 21 09:46 hbrdisk.RDID-9786ae39-cd3a-4773-be63-cd1bc3641d59.14.175750085646519.vmdk
 52.0K Sep 21 09:46 hbrdisk.RDID-ae17cfad-c8d8-460c-99a1-8f26ff1133b9.13.43820857661344-delta.vmdk
   375 Sep 21 09:46 hbrdisk.RDID-ae17cfad-c8d8-460c-99a1-8f26ff1133b9.13.43820857661344.vmdk
  4.1K Sep 21 09:46 hbrgrp.GID-d69c6cad-42a5-474a-86c4-c3158d1a3b42.txt
 25.0G Sep 21 09:46 vcenter-tm01-flat.vmdk
   473 Sep 21 09:46 vcenter-tm01.vmdk
 60.0G Sep 21 09:46 vcenter-tm01_1-flat.vmdk
   476 Sep 21 09:46 vcenter-tm01_1.vmdk

As you can see the folder contains a lot of files we are familiar with… Especially the vmdk files and the vmx files is something we can work with. So how would we get this vcenter up and running. Lets look at the vmxf file first as that will reveal the original name of the vmx file:

<vmxPathName type="string">vcenter-tm01.vmx</vmxPathName></VM></Foundry>

Next I am going to copy the “.nvram”, “.vmx” and “.vmxf” file and give them the name “vcenter-tm01.nvram” etc.

cp hbrcfg.GID-d69c6cad-42a5-474a-86c4-c3158d1a3b42.6.vmxf.17 vcenter-t 
vcenter-tmp.vmxf

So now I have all the files I need with the right name… Next I will first “unregister” the original vCenter Server virtual machine… just to avoid any weird issues. I list all the virtual machines registered against this host first:

vim-cmd /vmsvc/getallvms

Now that I have the “vmid” I can unregister the original virtual machine:

vim-cmd /vmsvc/unregister <vmid>

Now that the original virtual machine is removed unregistered from the host, I should be able to register the “new” vCenter Server virtual machine… aka the replica.

vim-cmd /solo/register /vmfs/volumes/4f228789-84f6b84c-e17e-984be1047b16/vcenter-tm01/vcenter-tm01.vmx

Lets break that one down just to be clear:

vim-cmd /solo/register /path/to/vmxfile/filename.vmx

This command will return the “vmid” of the virtual machine we just registered. Now we can power it on…

vim-cmd /vmsvc/power.on

Now it sits there for a while, and when I log in with the vSphere Client and check the host it is running on I see this message that says “the virtual machine might have been moved or copied…”, I answer it by saying that is was copied and now the vCenter virtual machine boots up and I can login again. Yes there is an orphaned vCenter Server instance there, and you will need to clean that up… also there might be some obsolete files in the folder of this replica, and you might want to clean those up as well. Anyway, the vCenter Server virtual machine is up and running again, and that was the goal of this exercise right 🙂

Protecting vCenter Server – HA or Heartbeat?

Duncan Epping · Sep 19, 2012 ·

At VMworld during one of my group discussions there was a discussion around using vSphere HA or vCenter Heartbeat to protect the vCenter Server. Coincidentally it is something that we recently discussed internally on Socialcast and I figured I would give my thoughts on this topic. My answer was short and simple: It depends.

Yes I bet some of you saw that coming… But let me elaborate. vCenter availability is crucial in my opinion when it comes to operating your environment. However your environment is not about vSphere. Your environment is not really about virtual machines. Your environment is about the services that you offer!

Your service level agreement typically is based on up-time of the service, makes sense right. No one really cares about the management platform, well I do and you do but your customers probably do not. Your customers care about the availability of their service.

Will their service have an interruption when vCenter is down is the question you will need to ask yourself. In most cases the answer will probably be no, and in those cases you will need to ask yourself what the downtime is you can afford from a management perspective. Is a minute or two okay? Than vSphere HA can help you and there is no need for Heartbeat or other complex clustering solutions. If a couple of minutes is not acceptable than Heartbeat is an option.

If there is a service interruption for the customer when vCenter is down (for instance in a test / dev cloud where provisioning processes are key, vCloud Director, View) you should consider using vCenter Heartbeat. Again, it all depends on your service level agreement. In some cases vCenter availability is crucial, in other cases a downtime of minutes is within the defined boundaries. The answer remains, it depends… it depends on your use case and service level agreement.

My vCenter Server 5.1 appliance crashed and I was using VDP… now what?

Duncan Epping · Sep 19, 2012 ·

I had this question this week, what if I am using vSphere Data Protection (VDP) and my vCenter Server appliance (VCVA) crashes… well lets just test it.

I just killed my vCenter Server appliance and deleted if from disk. Next step is to get a brand new vCenter Server appliance up and running. So I deploy a brand new VCVA first. As I have pointed my vSphere Client directly to a host I will need to login to the commandline to configure my networking, you can use vami_config_net but also Yast.

/opt/vmware/share/vami/vami_config_net

Next I go through the regular setup and configuration steps. Create a Datacenter and a Cluster and add some hosts. Now I see my VDP appliance again in my inventory… but I don’t see those nice shiny VDP icons. So how do I get those back? Well that is simple, just register the appliance to the new vCenter Server:

Point your browser to the VDP configuration web page
https://<ip address or name of vdp appliance>:8543/vdp-configure/
Click on the “configuration” tab
Click on the lock to unlock the config
Now enter your appliance password
Provide the new vCenter Server details (in my case they are the same as the old so I just provide the password of the vCenter Server appliance)
Reboot the VDP appliance
Reboot the vCenter Server appliance

Now open up the Web Client and …

Click the “vSphere Data Protection” option in the left pane of your Web Client
If you see the “Not Connected” status, click “Connect”
That is it… now you can restore VMs again

Back to Basics: Using the vSphere 5.1 Web Client to create a Cluster object

Duncan Epping · Sep 12, 2012 ·

We’ve shown you how to create a vSphere Datacenter object, next we are going to create a cluster object. Again, this is fairly straight forward:

Click on “Create a Cluster” in your “Getting Started” tab.
Provide a name for your cluster and tick “Turn On” for both “DRS” and “vSphere HA”.
Click “OK”.

We will not tweak any settings around HA and DRS, the defaults should work for most, although I would prefer to use the “Percentage Based” admission control policy. For more details I would like to recommend reading the vSphere 5.1 Clustering Deepdive. [Read more…] about Back to Basics: Using the vSphere 5.1 Web Client to create a Cluster object

Back to Basics: Using the vSphere 5.1 Web Client to create a Datacenter object

Duncan Epping · Sep 11, 2012 ·

I am going to assume you already have vCenter 5.1 up and running, if you don’t read this article. Once again, this is a “Back to Basics” series, so don’t expect deepdive info here.

First point your browser to the vSphere Web Client. The vSphere Web Client can be found at: https://<IP address or DNS name of your vCenter instance>:9443/vsphere-client/. Now you will see is a question if it is okay to install the “VMware Remote Console Plugin” as shown in the following screenshot.