migration of VM cold from ESX 3.5 to 4.0 with old to new hardware

HI, we currently have some s IBM X 440 (Intel Foster, think Pentium 4s) we are looking for plans to migrate to esx 4.0 and with this, it seems that we need a major hardware upgrade.

While we are looking at is some Intel Xeon X 3323 machine like some DELL T100 or T30 or some of the new stuff with E5504 (Nehalem) server as some IBM system x 3400 M2-based.

So, I would like to know if there are any additional steps I should do prior to a cold migration (assuming you cannot vMotion between the two hot), with the new system added to the farm. Or is it simply impossible and we need to recreate the images from scratch?

We would like to make two plans is to use the migration within the farm tool or a cluster or w/e they call it now and the other one is when it breaks and we do something more complicated.

It would be like:

(1) add new machine of the same farm with add-on host in the VI client

(2) migrate virtual machines more with the migration tool.

Or if this fails due to network problems, you can:

(1) use vmkfstools-i to move the virtual disks to a space of EXT3

2 (a) use console / ubuntu live CD to mount a USB key and move the virtual disks to the new machine

SCP use 2B) to do the same as above

(3) to recreate the VMX file to the new machine

Here are the General steps (spreading things like VMs off, or update tools and etc.), and I was wondering if they would at least work or any who tried such migration between old and new materials.

Thank you

Ok. Since you have not vCenter, you can turn off the virtual machines and just copy the VM via SCP.

After this opening Datastore Borwser in VI client, find the .vmx file, right-click on it, "add to the inventory.

---

VMware vExpert 2009

http://blog.vadmin.ru

Tags: VMware

Similar Questions

  • The migration of the VM from ESX 3.5 data center to data center inside the same building Vsphere

    Hi experts,

    Currently, we have 5 servers ESX 3.5 and a San in a shelter in the United Kingdom. This kit is now over 3 years old and the company replaces the complete kit with a new SAN, new servers and Vsphere 4.0.

    We have the opportunity to get new equipment to the top and running in the same shelter in Britain and are therefore able to run cable network between the two cabins if necessary.

    What is the best way to migrate existing virtual machines from the old environment running to the new environment running Vsphere ESX 3.5? As mentioned only the two cabins will run in the same shelter so nothing needs to go on a WAN link.

    IM keen to not load the machines on a USB key and move like that if I can help it. It appears from the research you cannot VMotion from one datacenter to another data center, however I can Storage VMotion between the two by using a method of migration cold?

    Any help will be appreciated, thanks

    agile1983 wrote:

    Disconnect a host ESX to the old environment, connect it to the new environment. (this means now that the old host as part of the new vsphere cluster can still see the old SAN?)  Then use this host as the link between the two San as you can see both of them?)

    Yes, presentation of the old drive will still be available on the assumption that it was not presentation of your San.  You can use a transit Host, which means that all the LUNS of the old environment and the new are presented to this host, but there will be a migration in a timely.  You have to vMotion invited to this host, unplug off the old environment and then in the new sVMotion (move the host and data store) to the new.  When this is done, unplug this transit host environment and add in the old, vmotion... Rinse and repeat.   Ideally, a presentation of the new LUNS to the old ESX host would be much faster.  In this way, you can bring your old environment together in the new. Make sense?

    When I disconnect and reconnect the old host to the new environment, which also happens to the virtual machines on this host? I need to move temporarily turned off?

    all comments will continue to operate without interruption.

  • Update Win 7 Starter to Home Premium operating system from a hard disk of the laptop with old?

    I have a netbook with Win 7 Starter.  I have an old laptop that the motherboard is dead hard disk.  I would like to transfer the Win 7 Home Premium OS from the hard drive of my netbook.  Since I already own the licence of this OS, is it possible to transfer?

    If Windows 7 Home Premium came preloaded on the old computer where the motherboard is dead, the answer is no. If the Home Premium license is a retail upgrade or full version, then all you have to do is use the key and product upgrade Starter to Home Premium.

    If the Windows 7 Home Premium license you have access to is a retail version update or complete, you can use the product key and the Express upgrade from Windows 7 Starter to Windows 7 Home Premium. First of all, check that the edition of Windows 7, you are upgrading is already enabled (if it isn't, you will encounter complications and that you might start all by performing a clean installation). Click Start, type Anytime Upgrade, click on the option to enter a key, enter the key of Windows 7 Home Premium, when asked, click Next, wait while checking the key, accept the license agreement, click on upgrade, wait while the software upgrades, (it may take 10 minutes or more depending on the if updates are required) your computer restarts automatically, after the reboot, Windows 7 will notify you updating the computer, the computer will restart once more automatically and will be completed the upgrade, a window will appear notifying the upgrade was successful and your computer is ready to use, click Close, you should be upgraded to Windows 7 Home Premium files the stored settings and programs.

  • Migration of VMs from ESX to ESXi 5.5 4.0

    Hi all

    What would be the best way to migrate virtual machines running cluster ESX 4.0 to 5.5 ESXi Cluster.

    In my view, there are two ways to do:

    1. Map (VMFS3) LUNS to the new cluster ESXi 5.5
      1. Shut down the virtual machine under the old cluster
      2. Remove inventory under the old cluster
      3. Add the VMFS3 LUN to the title of the new group
      4. Add the server to the inventory
      5. Power on virtual machines
      6. Perhaps svMotion machine virtual of VMFS3 new VMFS5 data store.
    2. Migrate the virtual via Vmware Converter Standalone Computer Cluster again.

    I think that method 1 would be the fastest, but I doubt if it is really practical, especially considering that the same data store/logic unit number will be writable by 2 different versions of ESX 4.0 and 5.5 at the same time.

    And method 2 seems the best way to me before that this will give me a possibility to start the virtual machine on the old cluster conversion failed if V2V or the destination virtual machine has problems.

    With above I have also considered possible vmotion, adding the former ESX host 4.0 under the pile of 5.5 ESXi but Xeon Intel processors are quite old and being unfit for vmotion, designed to allow CVS too, but for this I must put the new servers CPU up to the level of the old CPU and post migration of servers will have to close all VM to put all the servers again at their optimum level by disabling EVC.

    So could someone please guide which would be the best way, because we intend to migrate about 150 virtual machines. Thank you.

    between steps 1 and 2 take the new backups just in case. You have no need to have both writable for each cluster between steps 2 and 3 remove the volume from the old cluster. Also, between cold steps 4 and 5, you can migrate them to the new from the old storage.

    -J

  • Migrating from ESX 3.5 to ESXi 4.1

    I am planning a migration of ESX 3.5 Uptade 2 to ESXi 4.1 Update 1 in September.  Material welcomes VI environment is in place for renewal of the lease.  I build the new environment vSphere and attach to the same storage shared as the existing ESX VI 3.5.  My plan is the following...

    1. Get and install a new hardware server (C3000 and BL460C G7).
    2. Installing vCenter 4.1 (leave vCenter in demo mode to expose all the features)
    3. Configure the plugin Update Manager vCenter
    4. Install ESXi 4.1 Update 1 on new hosts and add to vCenter 4.1
    5. Configure the new Cluster and configure HA and vMotion. (We are allowed for vSphere 4.1 Standard Edition)
    6. Linking hosts to Update Manager and sanitize with all updates.
    7. Configure virtual networks (host profiles are an option while in demo mode).
    8. Fix new hosts of VMFS existing databases.  (Data banks are VMFS version 3.31)
    9. Disconnect the Virtual Center 2.5 3.5 ESX host and add them to the new vCenter 4.1.
    10. Cold migrate VM ESX 3.5 hosts ESXi 4.1 bed and breakfast hosts
    11. Upgrade VMware tools on all guests.
    12. Upgrade all the guests computer virtual from version 4 to version 7.
    13. Detach the ESX host 3.5 since VMFS data warehouses.
    14. Remove the ESX 3.5 hosts vCenter 4.1
    15. Install all keys in license vSphere 4.1 (vSphere Standard Edition)
    16. Start the VM guests.
    17. Close and dismantle the old ESX 3.5 hosts.

    Any feedback is most appreciated.  Please let me know if I'm missing something.

    Then, you'd weigh your losses.  Do you have the characteristics of the hardware virtual v7 for these virtual machines or can you live with material v4?  Personally, I needed the changed block tracking which requires hardware v7.  It really comes down to what you need.  I recommend bringing them up to v7 but that's just my opinion.

  • Migrating from ESX 3.5 to 4.0

    Hello

    If someone does migration from ESX 3.5 to 4.0, is - anyone can share questions

    This product during migration and if there is no vmware migration documents or

    Thanks to the experience itself can someone share it here.

    Thank you and best regards,

    BSR Krishna

    Welcome to the Forums - I had no problems following the upgrade guide - http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_upgrade_guide.pdf

    If you find this or any other answer useful please consider awarding points marking the answer correct or useful

  • Upgrade from ESX 3.5 to the pain of VSphere 4.10

    Very well...

    I was able to make a storage VMotion of VM running on ESX3.5 of our old SAN in the new NETapp san... No problem... Power off the computer virtual, cold have migrated the host VSphere 4.1.  Improved VMtools, turned power off and upgrade virtual hardware... Save power-> reset the NETWORK card using DHCP!  Virtual network adapters are of type "flexible." I have reset the settings of network adapter originally static IP address and windows complains that another adapter that is hidden and not installed is configured with the IP address... I've seen this before... But the problem is that the old adapter is the exact same AMD VMware Net Adapter like the one recently developed to date.  Attempted to delete the thing hidden devices, but the device that is hidden is not - it is the same thing as what is currently in use...

    .. What's going on here?

    did you start DEVMGMT. MSC

    This must be done in the command line.  It appears your screenshot not started from the command prompt.

  • migrate between the Mac from different countries

    Hello!

    I have an old imac that I bought in Germany (running SnowLeopard) 8 years ago.

    Now, I live in Sweden and I think of buying a new imac here.

    Does anyone know if I could transfer all the settings and data using the migration assistant or the computers "speak different languages?

    It does not matter where the computer was purchased?

    This may seem like a dumb question but I have had this problem in my work with two windows computers and had to migrate manually all... I hope it works smoother with Apple?

    Thank you very much in advance!

    / Samzwo

    Regardless of where the computer was purchased, but if you run into problems with the Migration from 10.6 to 10.11 Wizard I don't know, it's a big jump.

  • From ESX 3.5 to Windows 2003 VM Workstation 10

    I copied a windows 2003 vm from esx 3.5 and want to run under 10 workstation.

    The problems seem to be: 1. He starts but not the mouse, etc. 2. try to restart and it will not stop. 3. try to upgrade of the tools, and it does not restart. 4 get error on buslogic scsi problem

    5. If the power off, then NTLDR is missing when restart it.

    Would appreciate some advice on how best to move the windows 2003 VM from ESX 3.5 to 10 Workstation

    Regards, Mark

    Hello and welcome to the communities.

    How did you move it, or what was the process? You might want to try VMware Converter, if you do not.

  • Needs to migrate a computer virtual from ESX3.5 to ESXi 5.0

    Hi team,

    Needs to migrate a computer virtual from ESX3.5 to ESXi 5.0.

    Please give me the steps.

    A note, hence the machine virtual vmx file is on your storage space.

    Right-click on the virtual machine, and then select 'delete inventory '.

    On your new host navigate to store data with the vmx - right-click on it and select "add to the inventory.

    Now you should be able to update your tools and your hardware,

    • migrate the production esx 4.0 to 5 new hardware esxi environment

      I intend to migrate my production esx4.0 vSphere esxi 5 environment (new hardware) environment. How can I migrate my vms to production that are hosted on esx 4.0 (3 hosts managed by vcenter) to new material, that is to say 3 new hosts running esxi5? I want to leave my production environment intact in case I need to back off because of problems if it is possible? I am aware that:

      «My upgrade VMFS-5 doesn't have a block size of 1 MB.» Why?


      Upgrade of VMFS-5 partitions retain the characteristics of the partition of the data store VMFS-3 original, including the block size of the file, size of 64 K subblock, etc.. To take full advantage of all the benefits of VMFS-5, migrate virtual machines to a different data store (s), delete the existing one and re data store - create using VMFS-5".
      so ideally, I want to create a new data store instead of to upgrade and move my VM prod on this.

      What are the options that are available to me? Thank you.

      I wonder if it would make a big difference to save storage space?

      30 years ago I probably would have said it makes a difference, but today, it is probably more expensive (i.e. is not worth spending time) to create a new data store and migrate everything to a few KB.

      André

    • Migration of Vcenter DB from SQL SERVER 2005 to SQL 2008 Express

      Hello
      I'll migrate the physical vcenter server to a virtual machine, then I'll install a new VM with OS 2008R2 and SQL2008. But I need the migration plan
      vCenter DB from SQL 2005 to SQL2008. VMware also recommends

      Note: 1) VMware recommends now IP address and host name the same information to facilitate the migration.

      (2) software migration to different vCenter Server, Manager of update or VMware Orchestrator. For example, Site Recovery Manager is not migrated.

      (3) move the VMware Orchestrator database. You must do it manually.

      We can give to vcenter server new name and IP and if yes what will be then problem occur after the post migration.

      Thank you

      vmguy

      It takes to keep the same name and IP address? If we will give different vcenter and IP server name then how will transfer of post stage

      If you can keep the same name of host and IP, this would make it so much easier.  That said, if you need to change the host name and IP address of vCenter you can run into issues where all your guests appear as disconnected. Usually, you can right click and choose 'connect', asked credentials for your hosts of ESXi, but after that they should remain connected.

      In addition, just in case I posted above another KB.

    • Query - moving from ESX 4.0 (cluster) to ESXi 4.1 (cluster) license

      Hi all

      Am very new to VMware, please bear with me.

      We have in our existing Production cluster, consisting of three (3) 4.0 ESX servers and the intention is to replace them with ESXi 4.1 (U1) (under license).

      The plan should gradually slide each ESX 4.0 Server and install ESXi 4.1 (U1) of an image from HP directly on top.

      No drama it (?), but what about the licenses...

      I have a few questions I have to date not been able to acqurie myself.

      1. With each of the VH in the Production cluster, are we able to move a server in the cluster, upgrade to ESXi 4.1 and go back to the same cluster?

      2. If NO to question 1, which would be the recommended upgrade path where there is one (1) cluster, three VH (currently ESX 4.0) and we replace with ESXi 4.1 (U1).

        We have x 1 vCenter Server Foundation 4 license and three(x3) vShpere4 licenses advanced.

        Must these licenses be updated too?

      Am deparate to find answers to these questions.

      Kind regards

      Cameron

      HI - welcome to the community.

      The answer to your question is YES - you can re - allocate your ESX 4.0 license to your hosts updated. the license is generic and can be removed from a host and added to the other using the License Manager.

    • Direct upgrade from esx 3.5 to esx 4.1

      Hello

      I've already upgraded to vCenter 2.5 to 4.1, now I'm upgraded by train from esx 3.5 to esx 4.1 and all of the articles and videos that I have read say that I need to download the upgrade zip file and do the upgrade through VMware host update utility (as I am only upgrade 2 hosts).

      However, when I try to download the zip file, the only option I get is

      ESX 4.1 Update 1 (updated the ZIP of ESX 4.0)
      Use this package with vCenter Update Manager 4.1 U1 or vihostupdate vCLI or esxupdate command line to upgrade ESX ESX 4.0 to ESX 4.1 update 1.

      Which allows an upgrade to version 4.0 (or if she says).  Can I use this zip file?

      I even went back through all the versions 4.0, and there is no upgrade for 3.5 anywhere zip file?

      How can I make this update of the utility of the upgrade using the host?

      Concerning

      Steven

      In my view, an error in the above steps.

      Are you using ESX and ESXi, you will need to download ESX 4.1 install ISO for upgrade from ESX3.5 to ESX4.1 driver

      You must use vCenter Update manage or esxupgrade.sh for upgrade. No other tool as vihostupdate, host update utility etc. are not supported.

      For more details from vCenter update manager, refer to the admin guide and for esxupgrade.sh, see http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1009440&sliceId=2&docTypeID=DT_KB_1_1&dialogID=170100028&stateId=1%200%20170096294

      Thank you

      Nithin

    • Error from ESX 3.5 to 4 NUMA

      Hi all

      I have a slight problem with all of my ESX 4.0 host. After the upgrade from ESX 3.5 4.0 the below error has popped up.

      Material:

      Firmware HP C3000 Blade chassis OA 2.32

      BL G5 465 Bios Rev A13

      2 x AMD Quad 2356

      24 GB of RAM.

      Error:

      TSC: 1137350434cpu0 ) NUMBER: 827 hitting detected imbalance between NUMA nodes.  Performance may be affected.

      I tried searching the forums for those who have the same problem but I had no luck.  Anyone who has ever run into something like this?

      Thanks for the help,

      James

      http://www.yellow-bricks.com/2007/12/28/memory-incorrectly-balanced/

      Duncan

      VMware communities user moderator | VCP | VCDX

      -

    Maybe you are looking for