When is it recommended to use a license file list for redundancy rather than true redundant servers?
• When there’s less system administration available to monitor license servers. • When load-balancing is needed for clients located far apart, e.g., London and Tokyo. You can make servers available locally, with remote servers available as backup. • License file list is more forgiving if you lose quorum. • License file list is not limited to three servers (any number will work). • Clients do not require reliable networking to a single node with license file list, so this is recommended where networking itself requires redundancy. 5.4 Counted vs. Uncounted Licenses The license file determines whether a license server is needed. If all the FEATURE (or INCREMENT) lines have a license count of 0 (unlimited) or “uncounted” (FLEXlm v6 or later only), then no server is needed. This type of license is called uncounted. Alternatively, if any FEATURE lines have a non-zero license count, then a server is required to count those licenses.
• When there’s less system administration available to monitor license servers. • When load-balancing is needed: when clients are located far apart, e.g., London and Tokyo. You can make servers available locally, with remote servers available as backup. • License-file list is more forgiving if you lose quorum • It’s not limited to 3 servers (any number will work); and for wide-area networks, you can make servers available locally, with remote servers available as backup. • Clients do not require reliable networking to a single node with license-file list, so this is recommended where networking itself requires redundancy.
