The topics in this section provide information about planning the Avaya Breeze® platform and Device Adapter upgrades to minimize outages during the upgrade process.
The following two deployment models minimize the down-time during Avaya Breeze® platform upgrade:
N+1
The N+1 server model allows one Avaya Breeze® platform server to be unavailable, provided the remaining N servers have the required capacity to provide service to the endpoints that got unregistered from the +1 node.
You can use the rolling upgrade method in an N+1 model to upgrade the Avaya Breeze® platform server. Rolling upgrade method minimizes end-user impact during the upgrade because the endpoints fail over to the active Avaya Breeze® platform servers that are either already upgraded or will be upgraded after the current platform node is upgraded.
Geo-redundancy
In a geo-redundant model, two data centers provide service to the endpoints. Every device has a Server 1 and a Server 2 that provide geo-redundancy in an event when there is an outage at one data center.
The time required by an endpoint or an MGC of an endpoint to fail over during upgrading the Avaya Breeze® platform server in a geo-redundant model is generally more as compared to the N+1 model. This is because the endpoints or MGC of the endpoints try to fail over to the primary server (S1) first. If S1 does not have the required capacity or if S1 is not reachable, the endpoints or MGC of the endpoints try to fail over to the alternate server (S2).
When you upgrade a Device Adapter Snap-in on an Avaya Breeze® platform cluster, the Device Adapter snap-in is upgraded on all the nodes within that cluster. The Device Adapter Snap-in upgrade process is service impacting. Unlike Avaya Breeze® platform, the Device Adapter Snap-in cannot be upgraded as a rolling upgrade.
