ESX 3.0 upgrade to Vsphere

Similar Questions

• ESX 3.5 upgrade to vSphere using Activation of Windows

  I'm trying to upgrade ESX 3.5 a customer to vSphere.   I have a single license of Windows Server 2003 Enterprise Edition and spin 4 VMS (clones) on a single ESX host.   (a real activation and 3 clones of the Windows VM already active)

  After that I've upgraded to vSphere each Windows VM will require reactivation of Windows.

  Can someone tell me what to expect regarding regarding the reactivation work or I will have to call Microsoft.  Microsoft will allow me to reactivate all 4 VM?  Is it the fact that the VM is clones impact of the process of reactivation with Microsoft?

  Thank you.

  Hello

  If Windows in the VM is already activated, it should not be necessary to "reactivate" once you upgrade to vSphere. I do updates all the time and have never had to reactivate windows.

  Best regards
  Edward L. Haletky VMware communities user moderator, VMware vExpert 2009, 2010

  Now available: url = http://www.astroarch.com/wiki/index.php/VMware_Virtual_Infrastructure_Security'VMware vSphere (TM) and Virtual Infrastructure Security' [/ URL]

  Also available url = http://www.astroarch.com/wiki/index.php/VMWare_ESX_Server_in_the_Enterprise"VMWare ESX Server in the enterprise" [url]

  Blogs: url = http://www.virtualizationpractice.comvirtualization practice [/ URL] | URL = http://www.astroarch.com/blog Blue Gears [url] | URL = http://itknowledgeexchange.techtarget.com/virtualization-pro/ TechTarget [url] | URL = http://www.networkworld.com/community/haletky Global network [url]

  Podcast: url = http://www.astroarch.com/wiki/index.php/Virtualization_Security_Round_Table_Podcastvirtualization security Table round Podcast [url] | Twitter: url = http://www.twitter.com/TexiwillTexiwll [/ URL]

• ESX 3.5 upgrade to vSphere 4.1

  What is the best way to migrate from ESX 3.5 to ESX 4.1, also VC 2.5 to 4.1 VC?

  Welcome to the community - follow the VMware Upgrade Guide - http://www.vmware.com/pdf/vsphere4/r41/vsp_41_upgrade_guide.pdf

  Curious to know why you aren't moving to vSphere 5?

• ESX 3.5 upgrade to VSphere 4, question of SAN.

  First time poster long time reader and disgester of all.  Thanks for all the info everyone.

  We manage all the IBM HS21XM blades.  We have all our warehouses of VM data on a San and the guests all have the ESX OS on the local blade HARD drive.  On the KB update: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1009039 it says on the step 5 Note ESX Server to physically disconnect the fiber during the upgrade.

  Since we are in a blade chassis that will cut all of our ESX host.  So it's kind of bad for us during the opening hours.

  My question is is in the chassis and by disabling the good enough to meet this stage port of host level or the fiber must be disconnected from the chassis?

  Thank you. Mike

  step 5 is just a security measure to ensure that warehouses data on SAN used be disturbed during the upgrade. It is not required of disconnect\disable SAN LUNS before starting the upgrade.

  Compared with 3.5, 4.0 upgrade mechanism is different, SAN data warehouses will not be disturbed in the current method of upgrade.  So far I have strength hear any question saying upgrade disturbed warehouses of data on SAN 4.0 updated.

  Kind regards

  Oumou khairy

• The trial of ESXi 3.5 to vsphere ESX 4.0 upgrade problem.

  Configure a test host ESXi 3.5 with 2 virtual machines running on it and I now want to upgrade to vsphere ESX 4.0, but where in the heck do I get the zip file needed to use Update Manager?

  I'll buy the Essentials bundle, but I want to test the upgrade before doing the actual upgrade, and I can't understand what I'm doing wrong.

  Help!

  It is for ESXi, and matter.

  This is the main directory of patches

  https://www.VMware.com/mySupport/download/

  .. But if you try to go to ESXi ESX, you can not upgrade, this is a regeneration.

• "No connection to the server of VR: does not not." after upgrade to vSphere 5.5

  As part of the upgrade to vSphere 5.1 to 5.5 along http://kb.vmware.com/kb/2057795 I've updated vSphere replication to 5.5.0.0 build 1309877. All rehearsals continued well then. I only add the new vCenter replication and it stopped for the old.

  After the migration of all VM including device just RV improved another 5.5 ESXi host I upgraded from original host and migrated the back of some VM. I noticed that only this VM is replicated again then. All other zeroes had "no connection to the server VR: does not not." and "Violation of RPO" messages (including RVS). If I migrate the original replication host virtual computer is restored. If I migrate to another connection from host to the server of VR is lost again - no matter what a host running VR.

  Any idea, please?

  Yes, it's possible, but I just wanted to rule out any more simple explanations first. I was worried especially when you said the VR server could not ping itself, but perhaps I misinterpreted what you were saying.

  In all cases, you can verify if this is your problem by looking for a line like this in the esx.conf of the hosts that you upgraded:

  / NET/vmkernelnic/Child [0001] / tags/4 = 'true '.

  If so, remove the line in the esx.conf and restart the host. Then, once the host is back, check that the network adapter assigned to the vmkernel is an accessible IP address.

  In my view, that the part "child [0001]" may be different on certain configurations if you do not find the exact line I've specified above, check around the lines part of [another] child.

• Adding more than one host ESX and the upgrade at the same time.  What is the order of preference of the operations here?

  We are budgeting for more licenses and hardware for 2014 and want to do immediately in January.  I am trying to decide what is the best order of operations for adding two vmware hosts additional to our current installation of vsphere and also upgrade our vsphere / esx 4.1 u3 for the latest and best.

  We have 3 Dell PowerEdge R710 running ESX 4.1 U3.  In this vmware cluster, there is a vcenter server 4.1 U3 virtual machine handle this.  The three servers are about 90% memory used so we add 2 additional servers.  Probably the Dell PowerEdge r.620 since we get up 2 in the space of a 710.  Storage is on a san EMC NX4 NFS which will become too but not yet, let's just deal with the vmware part.

  When adding additional r.620 2, should I install ESX 4.1 on them and join them to the existing cluster and THEN pass vcenter and each one esx?  I ask precisely because 90% of use on 3 current servers, I need 2 other servers to support the update operations take place.  They would be able to repel vmotioned vm while each host receives an upgrade at the same time.

  So which is the best way to go about adding of the hosts and the upgrade?  Would I add as 4.1, then they would be available as targets vmotion and so I have room to start the hosts one upgrade at a time?

  If I update vcenter to the latest version, it is comparable backwards and can manage the 4.1 hosts, but also hosts 5.x?  I guess version 5.5 is the last one I would get from VMWare?  It is right of ESXi, then, how is this ESX ESXi 5.5 4.1 upgrade?  How much storage space do I need for ESXi 5.5, as I'm dechatoiement out of these r.620 Dell and need to know what hard drive to put in.

  The steps that you must follow

  -Updated vCenter Server

  -Upgrade of the ESX hosts (because we do a updating of the material we will install 5.5 on our new guests and add them to the cluster and then dismantle our existing)

  -Upgrade VMWare tools

  -Update data warehouses

  ESXi 5.5 has these storage requirements:

  • Installing ESXi 5.5 requires a boot device is at least 1 GB in size. When booting from a local disk or SAN/LUN iSCSI, a 5.2 GB drive is necessary to allow for the creation of the VMFS volume and a scratch 4 GB partition on the boot device. If a smaller drive or logical unit number is used, the installation program attempts to allocate a region scratching on a separate local disk. If a local drive is not found, the scratch partition (/ scratch) is located on the disk virtual ESXi host, linked to the/tmp/scratch. You can reconfigure /scratch to use another drive or logical unit number. For best performance and memory optimization, VMware recommends that you leave no /scratch on the ESXi host ramdisk.
  • To reconfigure / scratch, see Configure the Scratch Partition of vSphere Client vSphere Installation and Installation Guide.
  • Because of the sensitivity of the I/O devices, USB and SD, the installation program does not create a partition scratch on these devices. Therefore, there is no tangible benefits to the use of the great features of USB/SD that ESXi uses only the first 1 GB. When installing on USB or SD, tent Setup devices to allocate a region scratching on a local disk or the data store. If no disk is local or data store, /scratch is placed on the virtual disk. You must reconfigure /scratch to use a persistent data store after the installation.
  • In Auto deploy facilities, Setup attempts to allocate a region scratching on a local disk or the data store. If no local disk or data store is found /scratch is placed on the virtual disk. You must reconfigure /scratch to use a persistent data store after the installation.
  • For environments that start from a San or use Auto Deploy, it is not necessary to assign a separate logical unit number for each ESXi host. You can co-locate areas scrape for several hosts ESXi on a single LUN. The number of hosts assigned to a single LUN must balance the size of the LUN and behavior I/O virtual machines.

• Slow IO performance after upgrade to vSphere 5

  Hi all

  I have a problem in our lab environment and I type some other brains in the community .

  First of all a brief overview:

  2 x Fujitsu RX300 S5 (FC HBA LP1150)

  1 x Fujitsu RX300 S6 (FC HBA LP1250)

  2 x Brocade 200E

  1 x Fujitsu Eternus DX90 (CF)

  1 x Fujtsu Siemens FibreCAT SX80 (CF)

  All devices are running with 4 G FC.

  Last week we updated our servers with the latest firmware (included HBA) and the latest vSphere 5 (updated 01 and the last patch-bundle). Everythings seems to run fine, after I've got svmotioned a few servers to get an empty data store. A few small servers (each. approximately 30 GB) need hours to get to the target data store. With CLI, I created a vmdk eagerzeroedthick to test the performance on our DX90. It took almost 10 minutes to create a 10 GB vmdk (about 17 MB / s; flow even showed DX90 performance monitor). I did the same on the FibreCAT and this storage is running normally with 170 MB per second.

  Now lets get things I did to track down the cause:

  1. I connected directly the first server with the DX90 (to avoid the fc switch)-> problem still there
     
  2. I went down the HBA firmware to version previos-> problem still there
     
  3. I installed the 4.1 vSphere update 02. I put only the investigation period and did test of 10 GB-> problem disappeared. for 10 GB, it took 39 seconds which is nearly 300 MB per second
     
  4. I installed (new installation) of the first version of vSphere 5-> surprise, the problem here is once again
     
  5. I installed ESXi 4.1 (I tested again and it took again 39 seconds for a 10 GB vmdk) and upgraded to vSphere 5-> problem is still there
     
  6. I tried all the way air, Fujitsu drivers customized for Emulex HBA and LUN parameters
     

  Writing performance monitor shows response time between 700 year 1400 ms and 17 MB per second with vSphere 5 to the DX90. With version 4, it is between 0 and 60 ms and nearly 300 MB per second. Only the SX80 works very well to any version (not support ALUA). Each unit works with the latest firmware.

  It is without doubt vSphere 5, what causes the problem. I can't find clues in newspapers or VMware KB.

  Does anyone have an idea or the same problem? If I can't find a solution in the coming days, I propose to prosecute.

  Thanks in advance

  Hi Martin,

  There is a similar discussion in a German community in vmware.

  The solution was simple, your table does not seem to support VAAI.

  If you follow the following article to disable VAAI.

  Turning off the feature in ESX/ESXi VAAI

  HtH,

  Ralf

• Upgrade to VSphere, from ESX3.5 to 4.1

  I wanted to see if anyone out there has had experiences that you want to share in what concerns the upgrade to vsphere esx3.5. Traps, precautions and things you would have done differently in hindsight. We are in the process of upgrading and wanted to have an idea of what could be a problem and what to be aware of.  We do not have a test environment that I can try this upgrade, then it is an upgrade of the production and I'm very cautious and careful.

  Thank you

  Shawn Smith

  I just finished upgrading a cluster of very large from ESX 3.5 to ESXi 4.1. First step was to upgrade vCenter, who has been somewhat complicated by the fact that I had to go from a 32-bit host to a new 64-bit host. Detach the database from a stand-alone server to SQL 2005, then to attach to a host of cluster SQL 2008 has been an easy victory, as he provided us with resilient layer of database. Then I let vCenter 4.1 run with the host ESX 3.5 for a week or two, to prove the cross-compatibility.

  I chose to do a clean install of ESXi 4.1 on each host. It could have been much longer than other methods, but I felt it was the best in the long term. This involved: removing host ESX 3.5 of the cluster, install ESXi 4.1 and all the drivers and the HP management bundles and join this new ESXi 4.1 host in the cluster. Using vMotion, I was able to do the project with absolutely no downtime!

  Finally, I have updated versions of material to version 7 and put to update VMware tools for all the virtual machines in a controlled manner which corresponded with our routine systems maintenance windows. I'm very uncomfortable with the scenario and happy to help someone who needs guidance.

  -Omid bougouin

• ESX 3.0.2 to Vsphere 4.0 update

  Hello

  Can I put a 32 bit ESX 3.0.2 installation to Vsphere 4.0?  The processor is capable of 64-bit (Dual-Core AMD Opteron 2218).  I've read articles that support a direct upgrade from ESX 3.0.2 to Vsphere 4.0, but I am concerned about the OS 32-bit to 64-bit Vsphere operating system upgrade.  Is this a factor?

  Thank you

  Damon

  You must use the ISO, but the installation will work fine as long as it's a supported upgrade path. I've done several 3.5 for vsphere 4 updates and without worrying about 32 to 64-bit.

  VExpert

  VMware communities moderator

  -KjB

• Upgrade to vSphere VI3

  Hello Experts!

  I'm currnetly running VI3 environment, and I want to upgrade to vSphere.

  I have a few new servers I want to install vSphere on also.

  Can I upgrade my server vCenter for sphere, then install vSphere on my new servers and still manage my pre-existing VI3 esx boxes using the new vCenter server running vSphere?

  Thanks in advance!

  I would create a new vCenter Server (VM) to manage all hosts. You need to keep your current online license Virtual Center server until you're completely out of VI3. Once this is done, you can retire the old virtual server Center Server and license.

  You can manage the VI3 hosts vSphere and the vcenter Server.

  What version of ESX do you currently use?

  Once you have the former hosts managed by the vCenter Server server, you can use the update/update Update Manager to vSphere/ESX/ESXi 4...

  VMware VCP4

  Review the allocation of points for "useful" or "right" answers.

• checks before the upgrade to vSphere

  Hi all

  my whish is upgraded to esx 3.5 hosts I already to vSphere.

  I checked HCL and it seemed to be possible, but, not being only not sure about x 64 CPU tried to build 1 x 64-bit OS on each host and I received a message that it was not possible.

  So I guess I can't upgrade to vSphere.

  Am I wrong? or I can do other than buying other servers...

  I am running DL380 G5 and DELL poweredge 6850

  THX in advance,

  Daniele

  Daniele,

  It looks like there DELL shipped this server with several different processors.

  The only supported are those listed in the VMware HCL for DELL PowerEdge 6850

  It goes the same for HP DL380 G5

  André

• The upgrade to vSphere + SQL Express to SQL 2005 + new vCenter Server

  Hello world

  It's the scénarion that I have today:

  A node just two HA/DRS cluster with vCenter 2.5 update 4 and two esx 3.5 update 4.

  The environment has increased enough to move from SQL Express to SQL 2005 standard. In the process, I want to upgrade the environment to vSphere and the vCenter move another box.

  I'm quite familiar with the process of vSphere upgrade but I donít know how to move the vCenter to another machine AND I do not know how to go from Express to the standard version of SQL in the process. (I have a SQL machine ready for use)

  I do not know how to handle all the changes here, I thought it would be nice to all move to the new machine and DB so that I could continue with the upgrade to vSphere, if this has meaning or not, I'm waiting for your ideas.

  I hope someone will give me some guidance on moving from SQL Express to SQL and how to move vCenter to another server (of course with a different server name and IP address)

  Thanks in advance for your support.

  I just did something very similar a few Sundays ago and it was really easy.  Refer to the section of the Upgrade Guide that talks about upgrading to vCenter on another Machine... (starts at p. 49).  We went from SQL 2003 32 bits on 32-bit Windows 2003 to SQL 2005 64-bit on Windows 2008 R2 64-bit.  Both are running as VMs - vCenter 2.5 is still there only as a license server - until I get all my hosts upgraded.

• intend to upgrade to vsphere 4.0 and need help

  someone has upgraded to vphere 4 again and suggestions or the steps necessary to succeed.  Thanks in advance.

  What are the types of hosts will you update? In most cases, you can use VMware Update Manager for ESX4i and vSphere 4.0, because you can't make a room upgrade with vSphere 4.0 CD. If your environment is lower, then 10 hosts, then use Host Update Utility to perform the upgrade, which is fairly easy or install base plug-in and configured VUM and sanitize it massively if you wish and plan accordingly with VMotion feature so that you have no downtime or need to use Storage VMotion, if you need to migrate between stores.

  Once you have upgraded your hosts all vSphere 4.0, you have an option to clean the ESX 3.5/Boot and files in directory existing using the 'cleaning-esx3' service console command. If you like not vSphere 4.0 performance for some reasons, you can restore to the State ESX 3.x as well by using the command line "rollback-to-esx3' which will reconfigure your bootloader then you can manually delete the service console vmdk file.

  I would start by looking at the guide to documentation how do more efficiently with planning in advance and prepare here http://www.vmware.com/support/pubs/vs_pages/vsp_pubs_esxi40_i_vc40.html

  Steps to follow:

  1 back up your database

  2 download the license file and the upgrade to vCenter 4.0 Server and components, point to existing ODBC connection to keep data of perf or clean install.

  3. switch to level the esx host using component VUM

  4. upgrade tools vmware and vmware hardware at level 7

  There is a video online of 4 steps casting presented by VMware its pretty good and solid foundation.

  Good luck!

  If you found this information useful, please consider awarding points to 'Correct' or 'useful '. Thank you!!!

  Kind regards

  Stefan Nguyen

  VMware vExpert 2009

  iGeek Systems Inc.

  VMware, Citrix, Microsoft Consultant

• Upgrade to vSphere and change equipment

  2 ESC PE2050 3.5U3 cluster with CX300 FC SAN

  I need to upgrade to vSphere - VC Inc., as well as change the PE250s to new hardware (also PE2950, but with the rear plate PCI-Express and more memory) and replace the Equalogic PS5000X iSCSI SAN

  (I find the CX300 with 10K disks being totally useless in terms of speed and virtually unusable in the current configuration)

  What would be the best way to do it?

  -upgrade of VC,

  -Add 2 new servers connected to the SAN iSCSI with a clean install of vSphere,

  -configure new servers,

  -do the old servers through to see Software initiator iSCSI SAN.

  -move the VM to SAN iSCSI with vMotion

  -give up the old servers & FC SAN

  Is it achievable?

  Thank you

  SEB

  Your research plan sound with the exception that you will use "Storage VMotion" to move the virtual machines, not of VMotion. By opting for vCenter/ESX 4 you'll do yourself a lot of favors too:

  1 iSCSI Performance is improved in ESX4 (even if you do not mention if you use hardware or software initiators)

  2 storage VMotion is integrated in vCenter 4 which will move the easy virtual machines

  3 storage VMotion is also much faster on ESX4, but I don't know that you'll see the speed increase from your source VMs are on ESX 3.

  You must also update all the tools and the virtual material on your virtual machines, this can be done with the new update manager.

  Edit: I forgot to mention that the EqualLogic iSCSI stuff is often times much faster than the fiber (according to the table). I wouldn't trust anyones blanket assertion that fiber is always faster than iscsi.