Rolling upgrades for App Vol 4

[vmit11]

I have two app volumes managers and my agents are configured with the registry setting to point to both managers, I am not using a load balancer. Is it possible to perform a rolling upgrade with this configuration? I would like to go from version 4.0.1 to 4.4.1(2103)

[Micheal_A]

Yes, you just do one AVM upgrade and then the other. I am assuming they both point to the same DB instances?

I would do this off hours and disable the service on AVM-2 while you upgrade AVM-1, if they are both connected to the same DB.

Once AVM-1 is upgraded, you can leave the service enabled while you upgrade AVM-2, if you are connected to the same DB.

[vmit11]

I thought the rolling upgrades would allow for zero downtime?

Yes both managers are connected to the same DB

[Micheal_A]

If they are both connected to the same DB and your Desktop pool VMs have fail-over (VIP) to the AVM's, then you can do a rolling upgrade.

1. Disable the AVM01 service and complete the upgrade.
2. Once AVM01 is back on line with the latest upgrade, disable AVM02 service.
3. Upgrade AVM02, confirm it is back online and continue on to the next AVM till they are all upgrade.

FYI, If you have more than two AVMs I would disable all of them but the two and then follow the steps above.

[vmit11]

To clarify this is the setup I have:

2 AVM's installed and connected to the same MS SQL Database
Gold image has registry setting for Manager1 and Manager2, pointing to the FQDN's of each AVM

I do not have any other configuration setup, does this allow for failover and rolling upgrades?

I am not familiar with VIP

[Micheal_A]

No, because only one of the two FQDNs will will be used as your primary AVM for your Desktop pool, without a Load Balanced solution with a VIP (Virtual IP) that will monitor both VM servers for connectivity.

You can do a DNS Round Robin, if you don't have LBs in your environment, but that will not give you a true load balance like an F5, Kemp or NetScaler.