Provision for Axidian EA/ESSO and CertiFlow server resilience

Created by Mikhail Baturinskiy, Modified on Mon, 12 May at 12:39 PM by L1 Support

Question:
Please specify your recommendations for provision of Axidian CertiFlow and EA/ESSO server resilience. Is it efficient to backup the servers and what components need to be backed up?
Please advise the best course of action in case of, say, server failure.

Answer:
The Axidian EA/ESSO and Axidian CertiFlow system store all the data (settings, licenses, authenticators, ESSO data, devices and policies) in the dedicated storage.
In Axidian EA/ESSO, the storage is the Active Directory, for Axidian CertiFlow - it is either Active Directory or Microsoft SQL.
We highly recommend to backup the storage first of all. With Active Directory, it is necessary to backup the Indeed Identity container and all of its sub-containers. With MS SQL, it is necessary to backup the whole of database. The backup copies can be created with any suitable software tool.

The Axidian EA/ESSO and CertiFlow server processes user requests and extracts/places data from/to the storage. No critical data is stored at the server, provided that encryption key files used to access the storage, reside at some protected storage, not at EA/ESSO/CertiFlow servers.

Thus, if a EA/ESSO/CertiFlow server fails, the users automatically switch to another available one. Moreover, you always can deploy a new server rather quickly.
For Axidian CertiFlow, it is recommended to set up a cluster using Microsoft IIS. Then the users could make use of other servers using the same web service address.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article