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

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output
1 comment
Read more

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu
Post a Comment
Read more

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: <START vmware-16.log> b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664
1 comment
Read more