VMware | vSphere 7 | Templates | Migrating template to another host

-

 Hello Techies! Welcome to Says Tech !

In this blog, we will understand the procedure to migrate any template from one host to another without converting it to a virtual machine.


Description:

As we know, VMs can be easily migrated to different hosts using vMotion or automated DRS.

Whereas, templates do not have option to self migrate or vMotion capabilities.


Suggestions:

1. Either you can convert the template to a virtual machine simply by:   

    Right click on the template --> Convert to a virtual machine --> use vMotion to migrate 

    Once done, you can convert the vm to a template again.

2.  Use reallocation / cold migration method


Steps Involved:

Here we will migrate the template from esx-01 to esx-02

1. Navigate to "VM Templates"

2. Determine the datastore for that template by accessing datastore tab on web client

3. After getting the datastore associated info, right click on the template --> Remove from Inventory

   


4. Navigate to the datastore --> Access the template folder --> Click on <template>.vmtx file --> Click on Register VM


5. On the register wizard, select any different host from the cluster and proceed to finish


6. Your template is now migrated to another host





Enjoy! 

Thanks,

Arvind Kr.

Comments

Post a Comment

Popular posts from this blog

VMware vSphere | ESXi Host | Namespace error while entering host into Maintenance

-
Image
Hello Techies! Welcome to Says Tech! In this blog, we will be dealing with an issue which we face while putting/exiting the host to or from maintenance mode. Description: After upgrade to vSphere 7, I found that my ESXi hosts were no longer able to go into maintenance mode and vice-versa. Maintenance task fails and it throws an error every time while putting or exiting the host to or from maintenance mode: Host cannot enter maintenance mode because it failed to enter Namespaces maintenance mode on the node.   Possible Cause: This can be happen if your environment is recently upgraded to vSphere 7 and the Workload Control Plan (WCP) service is either stopped or stuck. Troubleshooting Steps: 1) Access VAMI console by navigating to https://<vcenter_name_fqdn>:5480/ then click Services 2) Scroll down and check for WCP (Workload Control Plan) service status 4) Click on Start if it is stopped, or click Restart if it is already started or stuck 5) Try to put the host in Maintenance Mode
Read more

Nutanix | CVM | Host Upgrade | Kill Stuck Task

-
  Hello Mates, Sharing the knowledge regarding an issue which I faced during ESXi/Hypervisor upgrade via Nutanix Prism Elements Description: While upgrading ESXi/Hypervisor from Nutanix Upgrade Software console, the prism elements was running pre-upgrade checks. PS: This can work on any stuck task on Nutanix, just apply the flags/entities as per your need!! Issue Occured: Running task stuck at 10% or 30% or at any certain number for long duration. There was no option to abort the task or cancel it via console Resolution worked: 1. Login into any CVM and run progress monitor           progress_monitor_cli --fetchall                              or           progress_monitor_cli -fetchall| egrep "entity_id|entity_type|operation" 2. Take note of the "Entity ID", "Entity Type" & "Operation" 3. You have the above information now, please run below command to delete the active stuck task           progress_monitor_cli --entity_id="entity_id&quo
Read more

VMware vSphere | ESXi Upgrade | Software or system configuration of host is incompatible

-
Image
  Hello Techies! Welcome to Says Tech! In this blog, I will show you to handle the ESXi upgrade issue caused by VIBs installed and the procedure to remove them! De scription: During patch remediation from VMware Update Manager or Lifecycle Manager, it aborted the process by throwing some error: The upgrade has VIBs that are missing dependencies. Remove the VIBs or use Image Builder to create a custom upgrade ISO image that contains the missing dependencies, and try to upgrade again . Software or system configuration of host is incompatible. Check scan results for details. Troubleshooting Steps: 1. Check the scan output from "Updates" tab on the target ESXi host 2. SSH to the target ESXi host and run below command and check the mentioned VIBs                 esxcli software vib list 3. Remove the impacted vib by running below command:                     esxcli software vib remove -n <vib-name> 4. Perform a host reboot before running the upgrade again. Enjoy! Thanks, Arv
Read more