Skip to main content

Moving managed ESX host from VCenter to another VCenter

 Moving a managed ESXi/ESX host from one VirtualCenter Server/vCenter Server to another Virtual Center Server/vCenter Server (1004775)


Purpose

This article provides instructions to move an ESXi/ESX host from one VMware VirtualCenter Server/vCenter Server to another VirtualCenter Server/vCenter Server when using standard virtual switches on all ESXi/ESX hosts.

When moving a managed ESXi/ESX host from one VirtualCenter/vCenter Server to another, VMware recommends that you move the virtual machines and management kernel back to a Virtual Switch (vSwitch) from a Virtual Distributed Switch (vDS); then perform the migration. After the migration, recreate the vDS. If you are using vCenter Server 5.1 or later, you can use the export/import functionality of the vDS to move your existing vDS configuration. For more information, see Exporting/importing/restoring Distributed Switch configs using vSphere Web client (2034602).


Resolution

To move an ESXi/ESX host from one VirtualCenter Server/vCenter Server to another, remove the host from VirtualCenter Server/vCenter Server, then add the host to a new VirtualCenter Server/vCenter Server. This operation will not affect the state of any virtual machines running on the ESXi/ESX, the historical performance data of both the ESXi/ESX and its virtual machines will however be purged.



Removing the ESXi/ESX host from VirtualCenter Server/vCenter Server

To remove the ESXi/ESX host from VirtualCenter Server/vCenter Server:

  1. If the managed host is in a cluster, right-click the cluster. Set the Distributed Resource Scheduler (DRS) mode to manual anddisable VMware High Availability by deselecting Configure HA.
  2. Click OK and wait for the reconfiguration to complete.
  3. Click Inventory in the navigation bar, expand the inventory as needed, and click the appropriate managed host.
  4. Right-click the managed host icon in the inventory panel and choose Disconnect (wait for the task to complete).
  5. Right-click the managed host icon in the inventory panel and choose Remove.
  6. Click Yes to confirm that you want to remove the managed host and all its associated virtual machines.




Adding the ESXi/ESX host to a new VirtualCenter Server/vCenter Server

To add the ESXi/ESX host to a new VirtualCenter Server/vCenter Server:

  1. Connect VMware Infrastructure Client/vSphere Client/vSphere Web Client to the new VirtualCenter Server/vCenter Server.
  2. Click Inventory in the navigation bar.
  3. Expand the inventory as needed, and click the appropriate datacenter or cluster.
  4. Click File > New > Add Host.
  5. In the first page of the Add Host wizard, enter the name or IP address of the managed host in the Host name field.
  6. Enter the username and password for a user account that has administrative privileges on the selected managed host.
  7. Click Next.




    Copied from VM​ware site.

Comments

Post a Comment

Popular posts from this blog

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.
Post a Comment
Read more

Recreating a VMFS-3 or VMFS-5 partition table in ESXi 5.x

For this kind of issues you need to engage VMware support on this, following any part of this article could lead to more complex situation if not ran by an expert.   Symptoms Datastore does not mount because of a lost or overwritten partition table.   Purpose When a VMFS partition is created in ESX 3.x or ESX 4.x, it has a Master Boot Record (MBR) partition map. The MBR is written to the first 512 B block (LBA0) and contains the information where the (VMFS) partition starts and ends. ESXi 5.0 introduced VMFS-5, which uses a GUID partition table (GPT) for new datastores. When a VMFS-3 partition is created in ESXi 5.x and is later updated to VMFS-5, the original partition map (MBR) is maintained. If the partition information of a VMFS datastore is deleted or overwritten (for example, by a Windows system with direct access to the same disks), it is impossible to determine if the partition map was GPT or MBR. The only time you can be sure that a GPT partition map was used is if th...
Post a Comment
Read more

How to deploy an OVA in Cloud Director

  How to deploy an OVA in Cloud Director Yesterday I was in a call with a customer and we discussed uploading OVA’s into Cloud Director. I said sure that is no problem at all. Well then I started thinking how are you supposed to deploy an OVA in Cloud Director because I do not even remember how this is done. So I opened up Cloud Director and tried it for myself. I decided to make this blog post along the way to show you how to deploy an OVA in Cloud Director. As an added bonus I will also show you how to upload an OVA to the catalog. This way I can deploy the OVA over and over again. Environment information Cloud director 10.3 OVA How to deploy an OVA in Cloud Director In Cloud director I opened up the Applications section and selected “NEW” I am deploying an OVA so I selected “Add vApp From OVF”. In the screenshot below you can see all the steps involved with (in my case) deploying and customising the Usagemeter. Options to customise are for instance: Network settings, vApp naming...
Post a Comment
Read more