Cross vCenter Server VM migration without same SSO domain in vSphere 7.0.

-

 Hello All,

Today, i am covering the new feautres introduced in vSphere 7.0 where we can migrate a VM to another vCenter Server which is not joined to same SSO domain. 

It means, there is no need to have linked mode and same SSO joined vCenter Servers to migrate a VM to another vCenter Server.

All you need you have Network connectivity between the Source and Destination vCenter Servers and required ports should be allowed as well as have access at both the vCenter Server.

Below are the screenshots capture while moving a VM from one vCenter Server to another running on vSphere 7.0 version.

 Login on Source vCenter Server and choose the VM which we want to migrate. 

Right click on VM and choose Migrate option and then select Cross vCenter Server export option.


 

 

Click NEXT 

Put Destination vCenter Server FQDN, Username and Password and Click on LOGIN option.

Accept the thumbprint and click on Yes

 

 

 

 Click NEXT and Proceed further. Select Destination cluster on which you want to move this VM.


Click NEXT and Select Storage datastore, in my case, i have vSAN backed DS.

 

Click NEXT and choose the folder hieracy to place the VM.

 

 

 Click NEXT and choose the Network port group for the VM.

 


Click NEXT and review the details and if all OK then Click on FINISH to Start the VM migration.

 

 

VM clone operation task will initate and will take sometime depending on the VM size and Network throughput.


 

Once the task finished you will get the Cloned VM at Destination vCenter Server.

That's it. This is really a cool feature to migrate a VM from one vCenter Server to another one without worry about linked mode and same SSO domain things.

Thanks....

Comments

Post a Comment

Popular posts from this blog

How to migrate the N-VDS as the host switch to VDS 7.0 in NSX-T 3.x

-
Image
  Hello There, In this article, i am covering how to migrate the ESXi host switch from N-VDS to VDS 7.0 switch in NSX-T 3.2.x version. When using N-VDS as the host switch,  NSX-T  is represented as an opaque network in  vCenter Server . N-VDS owns one or more of the physical interfaces (pNICs) on the transport node, and port configuration is performed from  NSX-T Data Center . You can migrate your host switch to  vSphere  Distributed Switch (VDS) 7.0 for optimal pNIC usage and manage the networking for  NSX-T  hosts from  vCenter Server . When running  NSX-T  on a VDS switch, a segment is represented as an  NSX-T  Distributed Virtual Port Groups. Any changes to the segments on the  NSX-T  network are synchronized in  vCenter Server. We have an NSX-T environment running with NSX-T 3.2.2.1 version. this environment was designed and implemented with NSX-T 2.x version and that time we used the N-VDS as host switch configuration on the transport nodes bcuz VDS was not supported that time. 
Read more

vROPS appliances password remediation tasks failed from SDDC manager

-
Image
Issue details:-   Password remediation tasks on SDDC manager getting failed with below error. However, we are able to connect SSH with root password on the vROPS appliances, no issues with credentials. I checked Operations logs on SDDC manager and found below logs, indicating the SSH connectivity issues from SDDC to vROPS appliances. Tried to do SSH vROPS appliance from SDDC manager, getting below error... Seems some issue with ECDSA key.. Resolution:- SSH to vROPS appliance and retrieve the ECDSA ssh keys as below. Now, we have 2 options to update the correct SSH keys for vROPS appliance on SDDC manager known_Hosts files located at below location.   /root/.ssh/known_hosts   /etc/vmware/vcf/commonsvcs/known_hosts   /home/vcf/.ssh/known_hosts   /opt/vmware/vcf/commonsvcs/defaults/hosts/known_hosts First option is manually copy and paste the SSH key on all the known_hosts files and restart the SDDC manager services and then try to remediate the password again. it will be successful this
Read more

How to Import/Register a VM into vRA portal

-
Image
You can import an unmanaged virtual machine to a vRealize Automation environment. An unmanaged virtual machine exists in a vCenter but is not managed in a vRealize Automation environment and cannot be viewed in the vRA portal . Once you import an unmanaged virtual machine, the virtual machine is managed by using the vRealize Automation management interface. you can see the virtual machine on the Managed Machines tab or the Items tab. Please follow below steps to Import/Register VM into a vRA portal. Log in to vRealize Automation as a fabric administrator and as a business group manager. If you are importing virtual machines that use static IP addresses, prepare a properly configured address pool.  If you use bulk import to import a virtual machine with a static IP address that is allocated to another virtual machine, the import fails. Create a Blueprint and should not have even network attached as well. See below snapin. Create Network profile that shoul
Read more