Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
AES Redundancy
- Thread starter Spudmoooo
- Start date
There is very limited support for redundancy. Nice/Witness are not yet using 4.1 AES clients, so they do not yet have the ability to admin a backup server in the client.
AES 5.0 will introduce a more complete failover. Until then, a backup server is just a spare, sitting on the net, waiting for you to change the client admin manually to use the new IP of the spare.
4.1 client should be supported by Nice on the Perform 3 product later this year, and Witness 7.8 will support it (GA in August). With 4.1, backup AES can be setup, and if link to primary is lost, app re-establishes a link to the backup without admin. It does require that the backup have a license that matches the primary.
4.2 will launch in May with ENTERPRISE WebLM functionality, so license could be stored on third server (non AES for instance). Then, active AES gets license from the third server, if it fails, the backup AES gets license from the third server. Will reduce need to buy dup licenses.
AES 5.0 will introduce a more complete failover. Until then, a backup server is just a spare, sitting on the net, waiting for you to change the client admin manually to use the new IP of the spare.
4.1 client should be supported by Nice on the Perform 3 product later this year, and Witness 7.8 will support it (GA in August). With 4.1, backup AES can be setup, and if link to primary is lost, app re-establishes a link to the backup without admin. It does require that the backup have a license that matches the primary.
4.2 will launch in May with ENTERPRISE WebLM functionality, so license could be stored on third server (non AES for instance). Then, active AES gets license from the third server, if it fails, the backup AES gets license from the third server. Will reduce need to buy dup licenses.
Hello,
Cti, I beg to differ. I have recently designed AES configurations for both Witness and Nice in the last 6 months both with application fail over support between AES servers. It is important to reiterate that the AES servers DO NOT fail over. It is the responsibility of the applications that talk to AES to fail over to another server. Also keep in mind for redundancy purposes, you need identical licenses on each AES to support application fail over.
RJP
Cti, I beg to differ. I have recently designed AES configurations for both Witness and Nice in the last 6 months both with application fail over support between AES servers. It is important to reiterate that the AES servers DO NOT fail over. It is the responsibility of the applications that talk to AES to fail over to another server. Also keep in mind for redundancy purposes, you need identical licenses on each AES to support application fail over.
RJP
- Status
Similar threads
