Building a Private Cloud with vCloud Director-Part 14-Migrating VM from vSphere Infrastructure to private Cloud using vCloud Connector

In our last post  of this series we have learnt what is vCloud connector and what it does.

Now its time to see vCloud Connector in action. In this post we will learn how to migrate a VM from existing vSphere Infrastructure to a private cloud running on vCloud Director.

vCloud Connector has server/node type architecture where there will be one server and one node for each type of cloud. Also we require a node to be deployed for vSphere Infrastructure.

In my last post Installing/Configuring vCloud Connector I have deployed a server and also a node for my vSphere infrastructure. After that we have to deploy a new node for the private cloud (running on vCloud director)

I have already deployed the same and in below screenshot you can see one node by the name “vCC-Node-Pri Cloud”


Also I have registered this node with my vCloud Director instance


On vCloud Connector Server I have added the newly added node which is registered with vCloud Director


I can see both my node (for vSphere and vCloud director) listed here


Now login to vCenter Server using VI client and from home page click on vCloud Connector to launch below page. Click on + button to add a cloud.


From the drop down menu select the cloud name which you have specified in vCloud Connector server. In my case I used the name Private-Cloud.

Add the credentials which will be used to authenticate against the organization which is created in vCloud director.


Now I can see both my cloud (vSphere-Infra and private cloud) have been added to vCloud connector. We are all set to go now.


Select the cloud that is associated with your vSphere and select “Virtual Machines” tab to list the VM’s present on vSphere.

Note: Before migrating a VM from vSphere to vCloud using vCC 2 things we have to keep in mind:

a: VM should be in power-off state and the VM state should be reporting as stopped in vCC UI

b: There should not be any media attached to the VM

In my lab I am going to migrate a VM named “Server 2003”


Select the VM and click on Actions button to bring the available options and from that list select Copy


In Select Target Cloud select your Cloud corresponding to your private cloud. Give a name for the VM and optional description.

Also select the Catalog where this VM will be deployed and hit Next.

In my lav I have only one catalog called Dev Test.

Note: VM will be deployed as vApp in this catalog


Select the Org vDC corresponding to your organization (if you have more than one Org vDC configured under same organization) and hit Next.


Under Deployment Options  you can select “Deploy vApp after copy” and you have to choose the network for this vApp.

You can also select “Enable Guest Customization” and “Change SID” feature if you want.

Also you can chose a fixed Administrator password for the vApp that will be deployed.


On Ready to Complete page review your settings and hit validate.


Once validation is successful you will get a message like shown below. Hit finish to let vCloud connector do the magic for you.


Under tasks you can see a new task of copying the VM have been started.


Also you can monitor the import status in vCloud Director we interface.


You will see some activities in vCenter Server recent Tasks pane


You  can see the new vApp is being deployed if you select My Cloud option under your organization.


Also in vCC UI you will see a new VM under your private cloud now.


Hope this post is informational to you. Share this on social media. Be Sociable!!