Migration of virtual machines to vSphere 4.1 to vSphere 6.0

As the title eludes to, we are standing up a new physics 6.0 Server vCenter Server and need to migrate virtual machines of 4.1 6.0 guest hosts.  I'd love to take the time to create a script that does the following; However, before heading down this path, I wanted to do a ping of the group to see if someone has done something like this before or have pointers to scripts that perform some of these actions already.  Some background and concept:

  • Running 4.1.
  • A new physical Center of vCenter 6.0 will be deployed side-by-side with 4.1.
  • The existing configuration of vSphere HA allows for 1-2 guests down without impact to the virtual machines.
  • The two environment and will be Cisco N1KV, SAN access shared for the same data storages.
  • A new vCenter will be lifted.
  • A single host is identified and VMs evacuated to the remaining hosts.
  • This host will be in maintenance mode, removed from the cluster and close.
  • A clean install of ESXi 6 will be done and set up spec.
  • N1KV will be deployed.

To digress on the details at the moment... Now markets PowerCLI desired.  This idea is ad hoc and on the fly, so as I write this.

  • identify all the virtual machines associated with a specific data store - will need to work with the local client to schedule downtime for virtual machines
  • Stop the virtual machine
  • Remove the VM of the vCenter 4.1 inventory
  • to connect to vCenter 6.0
  • Add the virtual machine to the vCenter 6.0 inventory (and once we have passed the first host in the new cluster, automatically place the virtual machine by using the DRS)
  • Reconfigure the vmnic with the new Cisco 1000V dvs (will be the same name on both sides, but has a different ID)
  • pull in the keys and the values to a CSV and advancedsetting set to harden
  • Turn on the virtual machine
  • Perhaps a test of ping for the NETWORK card to check connectivity

The order in which the steps are performed can be switched around, as long as the desired end result is the same: migration effectively virtual machines between two disparate solutions with single medium sharing as a data store.  In which I realize will always be VMFS3.  New data stores VMFS-5 is another task for another time.

Thank you for your time, suggestions, links, etc...

@LucD - hi.

These steps are quite possible with PowerCLI.

See the script after skeleton, he probably needs some adjustments to fit your environment and requirements

$dsName = "xyz".

$vm = get - VM - $dsName data store

Stop-VMGuest - VM $vm - confirm: $false

Remove-VM - $vm VM - confirm: $false

Disconnect-VIServer-Server vc41 - confirm: $false

$vc6 = Connect-VIServer-Server vc6

$newVM = $vm | New-VM - DiskPath $_. ExtensionData.Config.Files.VmPathName - confirm: $false

# Suppose a CSV file with

# Key, value

# key1, value1

# key2, value2

$advSettings = import-Csv - UseCulture advSettings.csv

{foreach ($obj in $newVM)

$advSettings | %{

Get-AdvancedSetting - $obj entity - name $_. Key |

Game-AdvancedSetting - value of $_. Value - confirm: $false

}

}

Start-VM - $newVM VM - confirm: $false

$newVM |

Select Name,

@{N = "Available"; E = {Test-Connection - ComputerName $_.} Guest.HostName - County 1 - Quiet}}

Tags: VMware

Similar Questions

  • How to migrate a virtual machine of vsphere vsphere 4 5

    I have a vsphere 4 and a 5 of vsphere, I want to migrate a virtual machine of vsphere vsphere 4 5

    my method is export ovf model and deploy the model of the FVO in vsphere 5, but it shows "end of file EGGS reached while looking for: * hard.

    How can I work my problem

    Thank you very much

    Hello

    Why are you trying with VMware Converter?

    https://my.VMware.com/Web/VMware/info/slug/infrastructure_operations_management/vmware_vcenter_converter_standalone/5_0

    It's the right tool for this kind of tasks/migration

    However, if you share with us details about your environment, we can help you more accurately.

    Concerning

  • Is it possible to migrate a virtual machine between vcenter servers programmatically?

    Hi all

    My question is quite simple:

    -Is it possible to migrate a virtual machine between vcenter servers programmatically?

    Let's say we have two data centers:

    vcenter1

    -vm1

    -vm2

    vcenter2

    -vm3

    Is it possible to migrate vms between vcenter2 and vcenter1 programmatically? (or vice versa)?

    Also, I'm assuming that the appropriate VLAN and data warehouses across the different vcenters!

    Thank you

    Luis

    It is not possible, vMotion or migration live is in an instance of vCenter, it cannot be covered through two even if you have the data store accessible both vCenters and sets of the host. At best, you can unregister the virtual machine of vCenter 1 host and re-save as on vCenter 2 host, but once again, it is while the virtual machine is turned off.

    =========================================================================

    William Lam

    VMware vExpert 2009,2010

    VMware scripts and resources at: http://www.virtuallyghetto.com/

    Twitter: @lamw

    repository scripts vGhetto

    Introduction to the vMA (tips/tricks)

    Getting started with vSphere SDK for Perl

    VMware Code Central - Scripts/code samples for developers and administrators

    VMware developer community

    If you find this information useful, please give points to "correct" or "useful".

  • Problem with Migration hot virtual machines Hyper-V

    Dear support

    I am facing problem in Live Migration of Virtual Machine in Windows 2012 of Hyper-V R2 cluster. Here are the details for my current setup.

    Two windows 2012 R2 Datacenter even care Server (HV01 and HV02) both in cluster

    A Virtual Machine created the Volume share of Cluster (c:\Cluster storage\...)

    A network adapter dedicated to the management of server-> 10.0.1.11 (HV01) and 10.0.1.13 (HV02)

    A network card dedicated to Hyper v Virtual Machines-> 10.0.1.12 (HV01) and 10.0.1.14 (HV02) and allow networking option is disabled.

    A network card for the heart beats-> 10.0.20.1 (HV01) and 10.0.20.2 (HV02)

    A network card dedicated for Live Migration-> 10.10.10.50 (HV01) and 10.10.10.51 (HV02) and chosen to be used only for the live migration fails on cluster network settings

    I added the Virtual Machine Cluster Failover successfully without error or warning. When I do a quick migration his works fine but when I do live migration his error giving 21502.

    Please update what's wrong with my setup

    Hello

    Post your question in the TechNet Server Forums, as your question kindly is beyond the scope of these Forums.

    http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

    See you soon.

  • Require a process step by step for the migration of virtual machines to new VMware ESX hypervisor

    Hello

    I'm looking for the method step by step for the migration of virtual machines to new host ESX Migration both cold and hot.

    Scenario - I have two data centers running ESX host stand-alone (with VM) in Europe. I need to build the new ESX host in new Dataceter to Singapore.

    Need prerequisites, the methods available for migrate VMWARE virtual has new host ESX (in the new data center) with minimum downtime.

    It will be great if you can enumerate the markets or redirect me to documentation that I can use to create detailed steps as the target host compatibility check on VMs and so on.

    Please advice

    Concerning

    AVI

    The steps are correct. The virtual machine must be turned off (step 3).

  • How to migrate a virtual machine from the server with DAS to another server

    Hi guys,.

    questions. 'More' essential Kit. VMotion is available

    I have 2 physical servers, two of them have DAS (not SAN Central). SO I want to migrate a virtual machine on server A to server B. is it possible in this situation?

    Or should I have versions of more expensive VMWare do?

    Thank you
    Dmitry

    You can use clone. I would close first to the bottom of the virtual machine, but a VM slowed would be very nice clone. You can also use the VMware conveter. VMware converter can make a hot clone, including synchronization of last-minute changes, stop the source machine and put under tension the clone.

  • Free version of ESXi can support for configuration of start and stop virtual machines via vSphere Client?

    I have read and found some documents on ESXi.

    According to the documents, I know that ESXi free version does not support some advanced virtual machine configurations and does not support write to ESXi host permission. But when I download ESXi from vmware.com, I can't find the free version. He will always be a trial of the licensed version edition because I can always do the configuration of start and stop virtual machines via vSphere Client installation. I can also run scripts (lamw) pl in vMA to stop the ESXi host (authorization to write ok?)

    Then I confused. How can I get the really free version of ESXi? Or will the free version after 60 days of evaluation?

    Start/stop above configuration is in vSphere Client via 'Configuration'-> "start/stop VM"-> "Properties"... «-> "Allow the virtual computers start and stop automatically with the system" actions setting and stop virtual machines can be configured to "comments"turn off computer"or"Suspend".» Can any body tell me if it's supported by ESXi free edition?

    Is the free version of vSphere Client too? Because when I use the vSphere Client, he told me that I have 60 days of evaluation. This confused me again. I think that vSphere Client is always free, am I right?

    Any suggestion or advice is much appreciated.  _

    Micky

    Configuration of start and stop virtual machines is available with the free version and licensed, with the free version you would be configured everything via vSphere Client, where as with a licensed version, you can optionally use scripts to configure it and also issue restarts/stops using scripts.

    Second, shutdownHostViaSOAPAPICall.pl for the version licensed and free of ESX (i), this script will work in both free and licensed because it uses direct SOAP calls emulating the vSphere Client communication. Take a look at the documentation for details, but this of course is not supported by VMware.

    =========================================================================

    William Lam

    VMware vExpert 2009

    Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

    Twitter: @lamw

    repository scripts vGhetto

    Introduction to the vMA (tips/tricks)

    Getting started with vSphere SDK for Perl

    VMware Code Central - Scripts/code samples for developers and administrators

    VMware developer community

    If you find this information useful, please give points to "correct" or "useful".

  • How to resize a virtual machine using vSphere client

    Hi all

    I have a virtual computer on an ESXi 4 server but I am not able to resize. So far I have stop the virtual machine in vSphere client, selected the settings then went to Hard Disk 1, Disk Configuration section everything is gray so cannot be changed. The type is listed as thick and the version of virtual machine is 7. How can I go on the increase in the size of the disk of this virtual, or any other machine also?

    Thank you

    Jamie

    Remember that you cannot increase the size of a disc if there is a snapshot, but if the option is gryed out, it looks more like a permissions issue.  You do that connected directly to the host of ESXi, or through vCenter?

  • Migrate a virtual machine with snapshots.  Works?

    In the past, moving VMs between databases or host with snapshots was deadly.

    It still happens in ESX4?

    ESX4 does not throw the warning, as did ESX3.5.

    You can migrate a virtual machine with snapshots, you can just see a different question.  You try to make a vMotion in vCenter?

    What is the symptoms you see?

    http://KB.VMware.com/kb/1005228

  • Problem migrating a virtual machine

    Hello!

    I have a problem when I try to migrate a virtual machine to the concrete only two hosts. I have no problem in other guests in my infrastructure. When I try to start this operation I get the following error message: "cannot migrate from esx1.domain.com to esx2.domain.com: the host CPU is incompatible with the function CPU requirementes of the virtual machine; problem detected the CPUID level 0 x 80000001 register edx.

    With other virtual machines, I have no problem and I can migrate from any host to any of them.

    Hi Eric,.

    Please check this link below:

    http://KB.VMware.com/selfservice/viewContent.do?externalId=1001131&sliceId=1

    Seems to be the answer to your problems.

    Please give feedback if this solves the problem

    Concerning

    If you find this or any other answer useful please consider giving points by checking the answer useful or appropriate.

  • Migrate a Virtual Machine like a physical machine

    Here's my situation...

    I had a virtual machine on a Virtual Infrastructure environment.  I wanted to migrate this virtual machine to another ESX environment.  The source environment is maintained by our IT Department and they will not help us or give us access to their environment.  Now we have a local administrator on the computer, virtual access, we decided to migrate the virtual computer as if it were a physical machine (physical machine to the coverter drop-down selection and installation of the agent on the source VM and when you are done uninstalling) in order to bypass interaction with HER.  The virtual machine migrated but very well and seems to work very well.  My question is, is there any potential problems migrating a virtual machine in this way (drivers, hardware, etc.)?

    Thank you!

    Your only way out is the it Department

  • Migration of virtual machines in ESX 3.0.1 & 3.5 to vSphere 5

    We have severely old stand alone ESX 3.0.1 and 3.5 servers and finally acquired new equipment and a cluster in VMware vSphere Essentials and try to migrate virtual machines, so we can remove the old assets. Using Converter Standalone 5 I only abe to pass successfully the Windows 2008 SMV ESX 3.5. All Windows 2003/XP virtual machines fail with this generic message "Unable to obtain material information to the computer selected."

    I tried various solutions of workaround mentioned around forums such as change the Linux guest OS during the migration and take snapshots of the source without result. Joint are recent newspapers Converter - will try and earlier version of the converter now as I have seen mention of this being a potential solution.

    Ah, I see - redefine was useful in some cases, when the Iso Coldclone was used.
    This CD is no longer available

    Just copy the complete directories - the vmdk formats are compatible - and where the new server don't like old VMS they can usually be adjusted with small text file modifications

  • Migration of virtual machines in ESXi 4.1 to 5.5 to new hardware

    I'm new to VMware and our company bought 4 new servers and a SAN to replace our old VSphere 4.1 installation of 12 year.  The old configuration consisting of a server VCenter 4.1 physics 2003, 2 Dell 2900 ESXi hosts and 1 MD300i SAN.  Gen9 again the Installer 4 HP DL360 (3 host 1 VCenterServer) and MSA 2040.  Can someone please explain to me what would be the best way to go about moving more of our VM current for the new hardware? I found this from a previous post here, but it does not move the virtual machine to a SAN to another.

    Migration of the VMs of ESXi 4.x to 5.5

    "If I understand your question, continue to build the new environment of 5.5 with your 3 hosts from scratch 'ignoring' your old hosts. Once your new environment up & running, connect 4.1 guests to your new server vCenter Server and vMotion to move virtual machines while they run to the new cluster (live migration without interruption).

    VMTools upgrades do not have place automatically during migration.

    Once your virtual machines on new hosts, update tools as usual and you can then also upgrade virtual hardware of your virtual machines.

    Virtual HW update is optional, though; If you do not have the VMs that need the new features you can skip this last step and keep them as they are. »

    TYIA.

    The previous answer is pretty good, but I would like to add a few elements.

    You can 'disconnect' your 4.1 hosts of your old vcenter with running virtual machines, and then when you connect the hosts in your environment of 5.5 it will import your VM running as well.  As long as you have properly configured virtual networks you can live migrate vmfs old host and the old store of data simultaneously via the web client as long as your esx license allows it.  Otherwise close your virtual machines down to 1 at a time to migrate them above.

    Alternatively, you can consider running your vcenter as a virtual machine within the cluster it manages.  This gives you some DRS and HA for vcenter, plus a 4th host for virtual machines.

    If you don't have additional license you can also install your new hosts of 5.5 and run for 60 days before that you upgrade your 4.1 licenses to apply to your new host.

  • Migration of virtual machines to vCD and again in a standard ESXi cluster itself?

    We currently have a relatively small cluster of ESXi (5.0.0 1489271) which uses a dedicated installation vCenter (5.0.0 1300600) and an instance of vCD (vCD 5.1.2.1068441).  Our goal is to move the virtual machines running in this configuration to our standard ESXi clusters (5.5.0 1892794) supported by installation of different vCenter (5.5.0 1891313).

    The instance of vCD seems to add additional parameters to the level of the virtual machine that prevents the VM of to be easily transferred out of the instance of vCD.  What we are looking for is a way to easily migrate these servers on and completely remove the vCD of the equation.  The only details around that we found cause downtime for exports out of vCD can be extended to reason the total amount of drive to the VM and VM level, which we really do not think it is an option to open a window of time to stop long enough to work through this process.

    Did someone went down this road before?  We have approximately 120 virtual machines in the cluster vCD using about 52 TB of disk.

    Maybe we're wrong understand something fundamental about the nature of migration of VMs on the vCD instance, but we have not been able to find many details on what options exist to make this move.  We have spoken several times with VMware support in this regard.  They mentioned a potential tool in the work within engineering migrate vCD to vCAC (which isn't really fall under our goal unless vCAC would then provide a clear path to return the virtual machines to a standard ESXi cluster).

    Any suggestions or ideas are appreciated.

    I am a colleague of GTC and wanted to just sent to our discussion of this topic with the help of VMware.  Basically, we should be able to Setup VMs in vCenter, outside of vCloud Director, pointing them to the same files VMDK and MAC then power off VM vCD and power on VM vCenter.

    : The NASA-EAST region

    Moment of validation: 2014-09-05 11:32 EDT

    Severity of the request for assistance: 4 - low

    Description of the request for assistance: we are looking for ways simple and less disruptive migrate VMS off vCloud Director and vCenter management.

    We have the advantage of a single principle in vCloud, managed by a vCenter and the network configuration is simple with no VXLAN.

    What are the problems with the realization of the following?

    vCD 5.1 is managed by vCenter 5.0, the final result will move VMs in vCenter even

    -Create a new virtual machine in vCenter that points to the same vmdk files as virtual machine in vCD you want to migrate, allocate same configurations of processor, memory, and network (we do not use the vCD with advanced networking)

    -Turning off the virtual computer in vCD

    -Once the vCD WHAT VM is off, power on VM in vCenter

    We must ensure that the VM vCD never gets turned on again and then when we are completely finished with all migrations of VMS in vCenter we abandon vCD.

    Of course there are details to help users migrate to how they use the vCD to vSphere vCenter client web interface or web interface.

    Entry date: 04/09/2014

    Since the opening of the case, I had interviews with several members of VMware support staff and these additional points were added.

    -Configure vCenter VM with the same vNIC driver MAC and like vCD VM vNIC

    -Rename VMDK files to make for easier management, or if not renamed then detach from the propelled out of vCD VM

  • Migration of virtual machines from a data store, and then delete the data store?

    Hello

    I have a future deployment this month and my Director wants to build a new RAID 6 array, create a store of data with the new table and then move all the VMS to the newly created data store.

    Then he asked me to take the old data store and remove it and the available space between the deleted data store and other stores of data in our shared environment. The question is when the new raid is created and vm has migrated to the new data store, which is the best way to remove the data store empty and make sure that the space available for other data stores? Any help would be appreciated...

    Greg ~.

    If all controls are met, you can go ahead and take it apart without any problem.

    I have re-iterate below checks:

    -No virtual machine is in the data store

    -The data store is not part of the cluster data store

    -The data store is not managed by the DRS storage

    -IGCS is disabled for this data store

    -The data store is not used for vSphere HA heartbeat.

    Especially highlighted 2 controls. Please note that SIOC can be enabled on the data without SDR photo store

Maybe you are looking for