Hi All. We're looking at upgrading from 2.12 to 2.14 this week, is anyone aware of any issues running an older version of the agent within floating pools against 2.14 App Vol managers? We've got lots of pools and images to update so it will not be done instantly after the App Vol manager upgrades but over the following week. We've got 2 App Vol Managers load balanced, am I right in thinking downtime is unavoidable?
So far I'm not seeing any problems in our very small environment, and when I asked tech support they said the differing versions are backward compatible. He said that I could update either component first. Since upgrading both I haven't seen any issues yet (though, it's early).
So far I'm not seeing any problems in our very small environment, and when I asked tech support they said the differing versions are backward compatible. He said that I could update either component first. Since upgrading both I haven't seen any issues yet (though, it's early).
Thanks. So did you upgrade the App Vol Managers first then stagger the agent upgrade?
In my case I upgraded the manager first (personal preference) but the support tech said it didn't matter which I did first.
We also have more than 1 loadbalanced server.
We mostly start with the manager (just a gut feeling), pull 1 appvol server out of the LB, upgrade it, put it back in the LB and remove the other servers. If it then works we upgrade the other servers as well and add them to the LB one by one.
Thanks Ray, the VMware upgrade guide states the below, which sounds like the manager services on all app vol managers needs to be stopped before the upgrade.
If you want to upgrade multiple App Volumes Managers which point to a central database, open services.msc and stop the App Volumes Manager service on each server. You must then run the installer on each server to upgrade App Volumes.