6 Replies Latest reply on Aug 14, 2019 10:04 PM by andvm

    6.7U2 Pre-Upgrade Checks and Rollback

    andvm Enthusiast



      Are there any pre-upgrade checks that should be done manually prior upgrading the VCSA from 6.5U2? (I have already started Phase 2 of the upgrade and pre-checks show nothing alarming other then some warnings for incomparable extensions which I do not intend to use further)


      Are there are any checks/best practices from experience that might cause install to fail so I take steps to check/remedy in advance?

      I know for instance that in the past the expired VCSA root password was not highlighted on the pre-upgrade checks but still caused the upgrade to fail.


      It's a single VCSA with an embedded or external Platform Services Controller.




      As for Rollback, I am planning to take a snapshot and a manual backup from VAMI.

      Not sure however in case the upgrade fails if I should just power down the new/failed VCSA and login to the ESXi of the current VCSA and simply power it on?




        • 1. Re: 6.7U2 Pre-Upgrade Checks and Rollback
          a.p. Guru
          vExpertCommunity WarriorsUser Moderators

          I usually check whether the password have expired (or simply set them) for root and administrator@vsphere local, and also run nslookup <IP-address> to verify proper DNS reverse resolution. If the integrated checks then don't show any more issues, you should be fine.

          If the upgrade fails, it's usually in a state where you can easily revert to the old one. However, if it fails at a late state there might be some things to consider if you want to revert to the old one, e.g. Domain membership, HA-Agents on the hosts, ...


          Anyway, with the major checks done, the upgrade should work as expected.


          The above assumes that you are upgrading from a supported 6.5 build. Not all of them may be supported (note the small "!" icon in the interoperabiliy matrix)!



          • 2. Re: 6.7U2 Pre-Upgrade Checks and Rollback
            andvm Enthusiast

            Logged in to VCSA with administrator account and logged to VAMI with root account. Both worked fine so password should not be expired.


            From which machine should I test nslookup and should I test again the current VCSA ip or the new (temporary one)?


            Entering just nslookup on the current VCSA shows:




            Confirmed it can resolve the hosts FQDN

            Pretty sure it was pointed to the DNS Server so not sure why seeing


            Yes upgrade supported as 6.7U2 came after the 6.5U2 version I have installed.

            information only says: For vCenter Server 6.7.0 onwards, applies to vCenter Server as well to Update Manager.....thanks for highlighting this.



            • 3. Re: 6.7U2 Pre-Upgrade Checks and Rollback
              a.p. Guru
              User ModeratorsvExpertCommunity Warriors

              Ok, go for it ;-)


              Btw. assuming that you've properly configured the DNS server address(es) on the vCSA, nslookup <IP-address> can be run from e.g. your PC/Server. It's only to ensure that the IP address will be resolved to the host name (reverse DNS).


              • 4. Re: 6.7U2 Pre-Upgrade Checks and Rollback
                andvm Enthusiast

                Will do, also out of curiosity does it matter at all if I have some hosts still going into maintenance mode whilst I upgrade or already in Maintenance mode?

                • 5. Re: 6.7U2 Pre-Upgrade Checks and Rollback
                  a.p. Guru
                  Community WarriorsvExpertUser Moderators

                  I'd try to keep changes at a minimum while upgrading vCSA. However, unless the host on which the vCSA runs, and/or is deployed stay are not going into Maintenance Mode, it should be ok. Please note, that you should set DRS to "Manual" during the upgrade to avoid initial placement, or movement issues with the vCSA.


                  • 6. Re: 6.7U2 Pre-Upgrade Checks and Rollback
                    andvm Enthusiast

                    a.p. - thanks it upgraded without any issues so just testing it remains fine for the next few days.