1 3 4 5 6 7 Previous Next 157 Replies Latest reply on Apr 18, 2008 3:56 PM by Badsah Go to original post
      • 60. Re: VI 3.5 Update 1 upgrade experiences
        xcomiii Enthusiast

        I just updated too, same problems. Luckily I can log in direct to the ESX hosts and startup VM's, but something is clearly wrong, as the ESX host is updating the resource pools (on the ESX) in an never ending loop. Any idea of what's my best option at this moment?

        • 61. Re: VI 3.5 Update 1 upgrade experiences
          FrancWest Novice

           

          Hi,

           

           

          I reverted back to the old VI client (left the VI server at latest version) and everything is stable so far.

           

           

          Franc.

           

           

          • 62. Re: VI 3.5 Update 1 upgrade experiences
            jasonboche Champion
            vExpert
            xcomiii wrote:

            I just updated too, same problems. Luckily I can log in direct to the ESX hosts and startup VM's, but something is clearly wrong, as the ESX host is updating the resource pools (on the ESX) in an never ending loop. Any idea of what's my best option at this moment?

             

            xcomiii, I rolled back to VirtualCenter 2.5.0 build 64192 (oh excuse me, that's the VC and VIC build number, not the VIM Installer number posted on the VMware download page...) using the following procedure:

             

            On the VirtualCenter Server:

             

            1.  Uninstall all VirtualCenter, Virtual Infrastructure Client, Capacity Manager, Converter, License Server, etc. software using Add/Remove Programs

             

            2.  Reboot the VC Server

             

            3.  Restore from backup your SQL or Oracle datastore from a point in time BEFORE the VirtualCenter 2.5 Update 1 upgrade scripts were run against it.

             

            4.  Install License server build 64192

             

            5.  Install the remaining VirtualCenter components build 64192 (if using a SQL Server back end for the datastore, don't forget to temporarily grant your VirtualCenter SQL account DBO on the MSDB database, then remove the account from MSDB DBO when finished!)

             

            6.  No reboot required after this point but I'd reboot

             

            7.  Your hosts may now show up disconnected in VirtualCenter.  Reconnect them, or remove/readd them.  It may be prudent to remove/readd them to roll back the VC agent version on the ESX host although I simply reconnected the hosts and am not seeing any issue yet.  Note I hadn't upgraded my hosts to ESX 3.5 Update 1 yet.  They remain at the original ESX 3.5 2/20/08 build.

             

            8.  VC cleanup:  Depending on whether or not VMs were added/removed between now and the tape back up you restored from, you may see some orphaned VMs in gray italics which you will need to remove from inventory.  You may also have some VMs that were added after your backup which now will be found in the "Discovered VMs" folder.  Move them to the appropriate folder.  If any changes were made to VC folder structure or stored template customizations, you'll need to re-address those as well.

             

            ESX host rollback

            I'd rebuild from scratch.  Never dabble with the integrity of your ESX host.  If you have an automated or scripted build, you can do this in less than 1 hour per host.

             

             






            [i]Jason Boche[/i]

            [VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

            • 63. Re: VI 3.5 Update 1 upgrade experiences
              xcomiii Enthusiast

               

              Thanks Jason.

              Is that the build 24201 from december-07 ?

               

              I forgot to mention that I first upgraded both my 2 ESX hosts to 3.5 U1 (yeah, silly me, forgot that VC needs to be updated first). I have a backup of VC, but that's not a big issue, as my enviroment is pretty small and I can recreate resource pools, foldes, permissions etc in a short time. So if I uninstall all VC related sw, delete the db, create a new db and then install VC with the correct build, it should work again ?

               

               

              • 64. Re: VI 3.5 Update 1 upgrade experiences
                jasonboche Champion
                vExpert
                xcomiii wrote:

                 

                Thanks Jason.

                Is that the build 24201 from december-07 ?

                 

                No. build 64201.  But I'm assuming that's what you meant.

                 

                VMware VirtualCenter 2.5

                Latest Version: 2.5 | 12/10/2007 | Build: 64201

                 

                 

                I forgot to mention that I first upgraded both my 2 ESX hosts to 3.5 U1 (yeah, silly me, forgot that VC needs to be updated first). I have a backup of VC, but that's not a big issue, as my enviroment is pretty small and I can recreate resource pools, foldes, permissions etc in a short time. So if I uninstall all VC related sw, delete the db, create a new db and then install VC with the correct build, it should work again ?

                 

                yep, and roll back your hosts to ESX 3.5.0 2/20/08 build.

                 






                [i]Jason Boche[/i]

                [VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

                • 65. Re: VI 3.5 Update 1 upgrade experiences
                  xcomiii Enthusiast

                  Sorry, a little typo

                  But exactly how do I revert two ESX hosts back to 3.5.0 ? Is there any docs on this or kb?

                  • 66. Re: VI 3.5 Update 1 upgrade experiences
                    jasonboche Champion
                    vExpert

                    As I said previously:

                     

                    ESX host rollback

                    I'd rebuild from scratch. Never dabble with the integrity of your ESX host. If you have an automated or scripted build, you can do this in less than 1 hour per host.

                     

                     

                     

                     






                    [i]Jason Boche[/i]

                    [VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

                    • 67. Re: VI 3.5 Update 1 upgrade experiences
                      FrancWest Novice

                       

                      Hi,

                       

                       

                      why revert back the host also ? I installed the host updates using update manager this week (not knowing that it was update 1) and it keeped working fine with the old VI server and client.

                       

                       

                      Franc.

                       

                       

                      • 68. Re: VI 3.5 Update 1 upgrade experiences
                        Engelsman Enthusiast

                        I never upgrade before looking at VMTN, so thank you all for paving the path

                         

                        Since we are planning on upgrading to VI35, I did an upgrade of VC202U2 to VC250Update 1 in a lab environment and it ran just fine.

                        I've downloaded and used the Virtual Center ISO file since the MD5 Checksum for the zip doesn't match. The ISO file seemed fine, so I installed from that.

                        I always install the stuff from the vpx dir instead of using the "autorun installer thingie".

                         

                         

                        To make things more confusing about the build numbers:

                        In the "vpx" dir there is a file called 2.5.0.64207. Also the properties of the viclient and vcserver setup files say product version 2.5.0.64207

                        In VC, when I go to Help, About my build numbers are build 2.5.0.84767. And then there is the build number of the VMware Infrastructure Management Installer: 84782

                        Would be "nice" to keep the buildnumbers in line......!

                         

                         

                        Regards,

                         

                         

                        Henk

                        • 69. Re: VI 3.5 Update 1 upgrade experiences
                          xcomiii Enthusiast

                          Franc, that was just what I hoped for. Currently all VM's are running on a 3.5 Update 1 host and the second host (in maintance mode) is also running 3.5 Update 1. Reverting both back without a working VC seems to be a little exciting to me. Surely I can revert the host which is in maintance mode, but how would I migrate them to that host without VC ?

                          • 70. Re: VI 3.5 Update 1 upgrade experiences
                            FrancWest Novice

                             

                            Hi,

                             

                             

                            why not first try uninstalling the VI Client only and install the old version and look how it goes ? In my case everything works fine with the old VI client and the update 1 VI server and hosts.

                             

                             

                            Franc.

                             

                             

                            • 71. Re: VI 3.5 Update 1 upgrade experiences
                              java_cat33 Master

                              Can someone from VMware please advise when the correct download is available for Update 1 (for ESX 3.5 and VC) - and also when the bugs have been fixed?

                              • 72. Re: VI 3.5 Update 1 upgrade experiences
                                xcomiii Enthusiast

                                Ah, thank you! Now I saved many hours of work, it works like a dream. Strange that the VI client is buggy though. Btw, I installed the VC update from the zip file, forgot to check the MD5.....

                                • 73. Re: VI 3.5 Update 1 upgrade experiences
                                  FrancWest Novice

                                   

                                  Hi,

                                   

                                   

                                  glad it worked. I mentioned this workaround a couple of post back already, but you and probably others overlooked it ?

                                   

                                   

                                  Franc.

                                   

                                   

                                  • 74. Re: VI 3.5 Update 1 upgrade experiences
                                    xcomiii Enthusiast

                                    Hi, yes I overlooked it in my frustration. Thank you for the solution.

                                     

                                    Maybe Jason can make this thread sticky or make this information better viewable to other that are upgrading?

                                    1 3 4 5 6 7 Previous Next