VMware Horizon Community
LJMCP
Enthusiast
Enthusiast
Jump to solution

App Volumes 2.12 to 2.12.1 Upgrade Procedure

The 2.12.1 Release Notes now state that an uninstall of the current AV 2.12 environment is no longer necessary when upgrading. 

Previously, I have been unmounting all appstacks from RDS hosts before upgrading AV Managers (two managers behind F5 LTM).  I've never been convinced this procedure is necessary and causes a complete outage to App Volumes environment, but it is specified to do so in the AV User Guide.

Yes, appstacks are removed from RDS hosts before the Agent upgrade, but I fail to understand why appstacks must be detached before Manager upgrade.

Are others detaching appstacks before upgrading Managers from 2.12 to 2.12.1?

Thanks!

Tags (1)
Reply
0 Kudos
1 Solution

Accepted Solutions
Ray_handels
Virtuoso
Virtuoso
Jump to solution

The reason you need to do this is because otherwise the manager has no knowledge of what happens with users that log off while the Appvolumes manager is not available.

We have 2 Appvolumes managers behind an F5 and thus we upgraded them one by one. No need to remove all active attachments.

When using the upgrade to 2.12.1 it doesn't ask you to remove the appstacks. We did a rebuild of the database (had some obsolete records due to upgrade from 2.6 to 2.9) so we installed it freshly. My guess is that you don't need to detach all appstacks when upgrading from 2.12 to 2.12.1 because the manager is always active.

View solution in original post

Reply
0 Kudos
4 Replies
Ray_handels
Virtuoso
Virtuoso
Jump to solution

The reason you need to do this is because otherwise the manager has no knowledge of what happens with users that log off while the Appvolumes manager is not available.

We have 2 Appvolumes managers behind an F5 and thus we upgraded them one by one. No need to remove all active attachments.

When using the upgrade to 2.12.1 it doesn't ask you to remove the appstacks. We did a rebuild of the database (had some obsolete records due to upgrade from 2.6 to 2.9) so we installed it freshly. My guess is that you don't need to detach all appstacks when upgrading from 2.12 to 2.12.1 because the manager is always active.

Reply
0 Kudos
MattVicos
Enthusiast
Enthusiast
Jump to solution

Looking at upgrading an pair of App Volume managers, in place from 2.12.1 to 2.14.2. If the installer doesn't unmount the appstacks and a prerequisite it to unmount/detach all appstacks/volumes what is the best way to achieve this?

Reply
0 Kudos
Ray_handels
Virtuoso
Virtuoso
Jump to solution

Please read the post on the other topic. You do not need to unmount all appstacks when upgrading. If you only have 1 manager I would suggest removing all users before upgrading. But mostly if you just have 1 manager it is a smaller environment to begin with.

sjesse
Leadership
Leadership
Jump to solution

I currently only have one appvolume server, and have upgraded from 2.9 to 2.13.3 over the last few years and I've never forcefully unattached appstack attachments. The only problem I've ever seen is when the appvolumes manager service is down, new appstack attachments won't happen. If you schedule your upgrades during a slow time you shouldn't have an issue. Our environment is a mainly active  9-5, so I've never seen a problem, people logged in never notice. When the upgrade appvolumes manager comes one the agents reconnect and a discovery process finds all the current attachments. I've been pushing for a second appvolumes manager, but I probably won't get that till the environment gets busier.