1 Reply Latest reply on Feb 13, 2019 12:45 AM by Ray_handels

    Upgrade Process Verification (2.14 -> 2.15)

    Anobix67 Novice

      Hello all,

       

      Currently looking at upgrading our existing test/prod infrastructure from AppVol 2.14 to 2.15. Reading through the documentation here: https://docs.vmware.com/en/VMware-App-Volumes/2.15/com.vmware.appvolumes.install.doc/GUID-C9E13A7C-729A-4ADA-AD98-A396557EF4DD.html it specifies the general steps to do the upgrade.

       

      My question is if everything needs to be updated prior to re-enabling connection, or if older agents/templates are backward (forward?) compatible until I can get the pools upgraded with the latest agent and the appstacks upgraded with the latest template versions. Trying to determine how long of a maintenance window I should expect for this process and how long people would be without their appstacks (I plan to do the process after hours, but to get a general idea of timing).

       

      Also, as a secondary question, at the point where you 'detach all volumes' I assume that disconnects the existing appstacks from the user's machines or is it still functional for them but one would be unable to get applications on a machine on a fresh login?

       

      Lastly, are there any specific steps that anyone uses for a clustered/highly available environment?

       

      Thanks.

        • 1. Re: Upgrade Process Verification (2.14 -> 2.15)
          Ray_handels Master
          vExpertCommunity Warriors

          What we normally do is we start with updating the managers. Because we have 2 in an F5 cluster we remove one from the cluster and upgrade the manager. If you upgrade it will not ask for detaching appstacks of all machines and if you have more than 1 Appvolumes manager there is no need to detach all appstacks. Make sure that you DO NOT overwrite the current database, otherwise all info will be lost.

          We then change the managers in F5 so all Agents will connect to the new manager. If this goes well we update the other manager using the same mechanism.

          After managers are updated we update the GI with the new agent and test is rather carefully to see if everything works and then migrate the pools one by one to make sure everything still works.

           

          We do not upgrade appstacks or writables (sometimes not even the templates) as long as it is not needed to do so and normally you would not need to upgrade appstacks or writables if you upgrade agent and manager.

           

          Regarding the time frame. Upgrading each manager (if everything goes well) will take about 15 to 30 minutes. Regarding the agent. I would suggest installing it on the GI and it depends how long it will take to update all of your pools.