In an Avaya IX™ Messaging High Availability (HA) environment, the licensing model is designed for redundancy and failover. The Primary server holds the master license file, making it the central point for license administration (B). This license is automatically replicated to the Secondary server by the system's HA service. However, the license copy on the Secondary server is temporary; it is time-stamped with a grace period (typically 30 days) and will expire if the Primary server remains inactive beyond this period (D). During a failover, the Secondary server uses its local copy of the license file to provide uninterrupted, full functionality, thus maintaining an individual license instance for operational continuity (A).

C. The license file is replicated by the core system's data synchronization service for High Availability, not specifically by the Mobilink application, which handles mobile device synchronization.

E. The license on the Secondary server is explicitly temporary and time-stamped to act as a grace-period license during failover, not a permanent one.

1. Implementing Avaya IX™ Messaging, Release 10.8 (June 2019), Document Issue 4, Chapter 4: Licensing the system, Page 101.

Supporting B & D: "In a High Availability configuration, you must install the license file on the Primary server. The system automatically copies the license file to the Secondary server. The license file on the Secondary server is time-stamped and expires after 30 days. If the Primary server is down for more than 30 days, you must contact your support organization to obtain a new license file for the Secondary server." This text confirms the Primary server is the holder, and the Secondary's license is time-stamped and expires.

2. Avaya IX™ Messaging High Availability and Disaster Recovery, Release 10.8 (June 2019), Document Issue 2, Chapter 2: High Availability, Section: "Licensing", Page 20.

Supporting A, B, D & contradicting C, E: "You install the license on the Primary server. The system automatically replicates the license to the Secondary server. The license on the Secondary server is valid for 30 days." This confirms the Primary holds the license (B), it is replicated (supporting the concept in A of the secondary maintaining a copy), and it is temporary (D), directly contradicting that it is permanent (E). It also attributes replication to "the system," not Mobil